[SERVER-32802] LVM snapshot restored node is added as member with invalid config error Created: 19/Jan/18 Updated: 22/Feb/18 Resolved: 19/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Ashutosh | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi Team, REPL [ReplicationExecutor] Error in heartbeat request to NODE2 ; InvalidReplicaSetConfig: Our replica set configuration is invalid or does not include us and primary NODE1 starts initial sync with secondary despite of fact that data is already present in NODE 2 data directory as it is snapshot backup of NODE1 ---> If mongodb is running on primary, lets say NODE1.We shutdown NODE1 using db.shutdowServer( {force:true}) command. Then, We, start NODE1 and add NODE2 as secondary, It becomes Secondary and inital SYNC is avoided, but throw below error 018-01-19T12:57:50.229-0500 I NETWORK [thread1] connection accepted from NODE2:60570 #49 (5 connections now open) The question is why this error is comming in mongo always and and what can be done to avoid that. Is there a way i can add node as secondary without doing shutdownServer command and intialsync using LVM SNAPSHOT BACKUP |
| Comments |
| Comment by Mark Agarunov [ 19/Jan/18 ] |
|
Hello ashutoshpandey89, Thank you for the report. To avoid seeing the error, you would need to reconfigure the replicaset to include the new node. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Thanks, |