Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
Repl 2017-03-06, Repl 2017-03-27
-
0
Description
Currently, rolling back a dropIndexes operation in the oplog requires a full resync of the collection documents and metadata.
This ticket proposes to extend the oplog entry for deleteIndexes to include the specification of the index that is being dropped so that we can recreate the index on rollback without any communication with the sync source.
Additionally, if there are multiple indexes dropped, a separate oplog entry should be generated for each dropped index.
Attachments
Issue Links
- is related to
-
SERVER-27096 applyOps should validate its ops to ensure idempotency
-
- Backlog
-
- related to
-
SERVER-29191 Dropping an index named "*" is ambiguous because createIndexes permits an index to be named "*"
-
- Closed
-
-
-
- Closed
-