-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
Repl 2023-11-13, Repl 2023-11-27, Repl 2023-12-11, Repl 2023-12-25
-
23
During initial sync, there is a period of time where the FCV is uninitialized. Feature flag checks during this time can throw an invariant (see SERVER-79317 for some more context). We should add a passthrough suite that runs initial sync in the background and pauses initial sync during the period where FCV is uninitialized. This will hopefully catch more cases where the feature flag check could throw the invariant, so that teams can proactively find and fix the problem.
- depends on
-
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
- is depended on by
-
SERVER-82246 Change isEnabled to invariant when FCV is uninitialized and audit feature flags
- Closed