[SERVER-64750] Only check isSelf for reconfigs when we have to Created: 21/Mar/22 Updated: 29/Oct/23 Resolved: 02/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc1, 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Vesselina Ratcheva (Inactive) |
| 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 2022-08-08, Repl 2022-08-22, Repl 2022-09-05 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Currently we depend on sameConfigContents to determine whether we need to check isSelf for a reconfig. This function only ignores the 'version' and 'term' fields of the config. However, there are other cases (e.g. removing the newlyAdded field for a node) where checking isSelf is not necessary. This ticket is to come up with a more precise condition for when isSelf check is necessary for a reconfig and to eliminate unnecessary isSelf calls. |
| Comments |
| Comment by Githook User [ 02/Sep/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |