We have several classes which use opObservers to keep in-memory state in sync with storage state. These include sharding state, authorization, tenant migration mtabs, maybe others. These will be run during logical initial sync when the system isn't necessarily consistent, and will not be run during file copy based initial sync. Both initial syncs have special code to fix some of these after the system is consistent. We should create a mechanism (either another opObserver, or expanding/renaming the onReplicationRollback opObserver) to handle fixing these cases after initial sync generally.
We might also consider not running the ordinary op observers during initial sync; this may require special treatment of FCV.
- is depended on by
-
SERVER-64601 Shard server mongod initialization is not run after File Copy Based Initial Sync
-
- Closed
-
- is duplicated by
-
SERVER-65251 FCBIS doesn't call to the onInitialSyncComplete ReplicaSetAwareService hook
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Backlog
-
-
SERVER-64628 More testing of adding nodes to sharded sets
-
- Closed
-