-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2016-09-19, Repl 2016-10-10, Repl 2016-11-21
-
0
During an initial sync, due to the way the collection catalogs are gleaned from the sync source, it is difficult to always accurately reflect the collection catalog at the time a given op was generated on the primary, at op application time.
Therefore, we must take extra steps to handle possible errors generated from certain ops that depend on accurate collection metadata. Some examples include collMod, createIndex, dropIndex, and createCollection.
For certain errors, we must ignore the error and subsequently ensure that another specific metadata operation is seen in the oplog stream before reaching minValid.
- depends on
-
SERVER-26097 Create unittests for initial sync idempotency project
- Closed
-
SERVER-26887 Idempotency of createCollection with options
- Closed
-
SERVER-26118 CollMod 'c' op: ignore metadata error when applying ttl-time changes
- Closed
- duplicates
-
SERVER-26202 Relax index constraints in oplog application
- Closed
- is depended on by
-
SERVER-25040 Initial syncing node maintains tmp collection from map reduce when primary has renamed it
- Closed
-
SERVER-25057 Initial sync fails on 2d index build
- Closed
-
SERVER-25487 Initial sync should fail and restart if it receives renameCollection op to apply
- Closed
- related to
-
SERVER-23932 Get collection info ASAP after listDatabases in DataReplicator::InitialSync
- Closed
-
SERVER-25403 DataReplicator initial sync should be resilient to applier failures
- Closed