[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:
Related
related to SERVER-47495 Ban force reconfig with "newlyAdded" ... Closed
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: SERVER-46347: Ensure that force reconfigs are not given a 'newlyAdded' field
Branch: master
https://github.com/mongodb/mongo/commit/d6dfe6f2d2c56b8f3ff63f8c0886caebbeaac0c5

Comment by Judah Schvimer [ 10/Mar/20 ]

Reconfigs are given a 'newlyAdded' field in two cases:

  1. When 'newlyAdded' already exists in the config and we're "merging" configs: SERVER-46351
  2. When the new config is adding a new node: SERVER-46344

Force reconfigs should do neither of these. We may want to do SERVER-46351 first, in hindsight, or split this ticket into two tickets, one for each case.

Generated at Thu Feb 08 05:11:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.