-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 8.0.0
-
Component/s: Upgrade/Downgrade
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2025-11-24
-
0
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
(v8.0 only since SERVER-67712 removed the test code affected by this bug)
In upgrade_downgrade_sharded_cluster.js, we force the secondary of the config server to get elected as primary using the replSetStepUp command.
If a background write (e.g. a periodic mongos ping) happens right when the replSetStepUp command is called, the secondary loses the election because it will see that it is not caught up with the primary.
We should retry the election if this happens (similar to what was done by SERVER-88459 for other tests).
- is related to
-
SERVER-88459 Use deterministic way than plain replSetStepUp command in jstests
-
- Closed
-
-
SERVER-67712 Remove Feature Flag for PM-2322
-
- Closed
-