-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Index Maintenance, Replication
-
None
-
Minor Change
-
ALL
-
Integration 2016-10-10
When the createIndexes command is replicated to a secondary, if the secondary sees an argument that it doesn't understand, it should return an error (and thus abort) rather than ignoring the argument. This impacts V2 indexes only, which are new with MongoDB 3.4.
- depends on
-
SERVER-26341 TaskRunner destroyed prior to task return
- Closed
- is related to
-
SERVER-24033 createIndexes command should write the spec of the index as created to the oplog
- Closed
- related to
-
SERVER-19642 createIndexes command allows duplicate element names in index spec
- Closed
-
SERVER-769 Validate top-level & index spec field names for the createIndexes command
- Closed