[DOCS-11115] Update documentation on adding a new replica set member to recommended adding with no votes Created: 11/Dec/17 Updated: 30/Oct/23 Resolved: 22/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 51 weeks ago | ||||||||
| Description |
|
When you add a normal replica set member, while it's in initial sync it still counts as a voting member towards the majority commit point, but its data is inconsistent, it cannot serve reads, and it cannot become primary. This can lead to a case where a majority of the voting nodes of the set are online but no primary can be elected. The recommended procedure for adding a new node to a replica set should be to add it with priority:0 and votes:0, and then once it has finished initial sync and transitioned into SECONDARY state do another reconfig to make it voting and electable. |
| Comments |
| Comment by Githook User [ 21/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: docs-11115 rs.add and initial sync |
| Comment by Githook User [ 21/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: docs-11115 rs.add and initial sync |
| Comment by Githook User [ 21/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: docs-11115 rs.add and initial sync |