-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
ALL
-
105
This is the same root issue as SERVER-79274. This method performs an initial check that FCV is initialized and later on attempts to get the FCV. But it's possible for the FCV to get unset in between those calls, e.g. if we are in initial sync (as seen in BF-30375) leading us to hit an invariant.
- duplicates
-
SERVER-79274 fCV checks can be racy if fCV is uninitialized in between the checks
- Closed
- related to
-
SERVER-79274 fCV checks can be racy if fCV is uninitialized in between the checks
- Closed
-
SERVER-79317 Provide more documentation and helper functions for case where feature flag checks could be run when fCV is uninitialized during initial sync
- Closed
-
SERVER-58534 Collect fCV in FTDC
- Closed