-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
ALL
-
If we run enableSharding and movePrimary on a database, we can cause it to be created (for the purpose of dropDatabase) without a "create" oplog entry. It appears that on the primary shard this does not cause a problem. On a non-primary shard the database will be created on the primary but not the secondary, so if a dropDatabase is run, it will create an oplog entry to delete a database the secondary does not think exists.
- is related to
-
SERVER-21700 Do not relax constraints during steady state replication
- Closed
- related to
-
SERVER-50532 Cannot require that database exists when applying 'dropDatabase' oplog entry
- Closed
-
SERVER-50540 Complete TODO listed in SERVER-46550
- Closed
-
SERVER-46221 Remove oplogApplicationEnforcesSteadyStateConstraints parameter and opCounters
- Open