[SERVER-46347] Ensure that force reconfigs are not given a 'newlyAdded' field Created: 24/Feb/20 Updated: 29/Oct/23 Resolved: 25/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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2020-03-23, Repl 2020-04-06 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'email': 'xuerui.fa@mongodb.com', 'name': 'Xuerui Fa', 'username': 'XueruiFa'}Message: |
| Comment by Judah Schvimer [ 10/Mar/20 ] |
|
Reconfigs are given a 'newlyAdded' field in two cases:
Force reconfigs should do neither of these. We may want to do |