-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-07-06
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In the sharding_stepdown_fcv_upgrade_downgrade_jscore_passthrough suite, the background FCV hook fails when a setFeatureCompatibilityVersion command races with a replication state change, i.e., a stepdown. Being this a transitional state, we have to tolerate this error at the test layer by adding a case in handleRandomSetFCVErrors for the relative error, i.e., 8531600, such that the background hook retries the FCV transition instead of failing.
- related to
-
SERVER-125978 Initializing FCV fails if any collections in the admin database have incomplete foreground index builds
-
- Closed
-
-
SERVER-129974 Tolerate setFCV error 8531600 (FCV document not found due to retryable error) in FCV background hook
-
- Closed
-