Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.5.5
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-03-06, Repl 2017-03-27
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

SERVER-30840 extend timeout in replsets/index_delete.js (3.4 only)

Closed

SERVER-87762 Remove unused ops for index dropping from kOpsMap in oplog.cpp

Closed

Assignee:: Judah Schvimer
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 06 2017 07:23:16 PM UTC
Updated:: Mar 11 2024 03:17:52 PM UTC
Resolved:: Mar 14 2017 08:14:25 PM UTC
Confidence Status Last Update:: 07/Mar/17 5:20 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates