-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Execution Team 2024-06-10
-
0
As mentioned in the linked BF, in the two node replica set we remove() one node before performing the reconfig, but the call to remove() shuts the node down too.
So now in a two node replica set the primary is left as the sole node alive and this means that it may step down. If the stepdown races with the reconfig and happens before the reconfig, then the reconfig command will fail as the primary cannot accept it.