-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
Oplog application should do exactly what the primary does, and not check FCV. FCV should only be checked on the primary. We should be able to invariant that FCV is only checked on primary nodes. This should make code like SERVER-49748 unnecessary. If in adding this invariant we discover places where we check FCV, we should understand why they do so and correct them.
- is related to
-
SERVER-49748 Initial sync should clone admin.system.version before any other collections
- Closed
-
SERVER-36498 Remove 'config.transactions' entries with 'state' field on shutdown in fCV 4.0
- Closed
-
SERVER-70202 Investigate calling serverGlobalParams.featureCompatibility.isVersionInitialized() in isEnabled()
- 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
- related to
-
SERVER-90971 Secondaries should call into lower level create collection API during oplog application
- Backlog
-
SERVER-88965 FeatureFlag checks must be performed while holding the global lock in IX / X if data can be written in a new format
- Closed