[SERVER-46344] When users run ‘replSetReconfig’ to add a new node with ‘votes:1’, add 'newlyAdded' field Created: 24/Feb/20 Updated: 29/Oct/23 Resolved: 09/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2020-03-09, Repl 2020-03-23 |
| Participants: |
| Description |
|
‘replSetReconfig’ will internally rewrite the requested config to give the new node’s MemberConfig (an entry in the ‘members’ section of the ReplicaSetConfig) a ‘newlyAdded’ field indicating that the set should not count it towards the current number of voters and that the primary of the set should automatically initiate a ‘replSetReconfig’ to remove the field once initial sync completes. Define a ‘new node’ as any node with an ‘_id’ field that is not present in the current config. Log any rewritten configs. |
| Comments |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'username': 'XueruiFa', 'name': 'Xuerui Fa', 'email': 'xuerui.fa@mongodb.com'}Message: |
| Comment by Githook User [ 06/Mar/20 ] |
|
Author: {'username': 'judahschvimer', 'name': 'Judah Schvimer', 'email': 'judah@mongodb.com'}Message: Revert " This reverts commit a4cc0fda2778dcc2c39d1e1d471fcfdd98534b38. |
| Comment by Githook User [ 05/Mar/20 ] |
|
Author: {'username': 'XueruiFa', 'name': 'Xuerui Fa', 'email': 'xuerui.fa@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 24/Feb/20 ] |
|
This should be implemented under an undocumented feature flag so that this behavior is not included in 4.4. |