Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.5.11
Affects Version/s: Backlog
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-07-31, Repl 2017-08-21
Confidence Status:
None

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

Currently in the 3.4 FCV of rollback, we handle rolling back renameCollection commands by resyncing the entire collection, which is inefficient and can lead to data corruption. In 3.6, with the implementation of UUIDs, we want to avoid full collection resyncs and fix the problem with data corruption after collections are renamed.

depends on

SERVER-30150 Two Phase Drops: rolling back cross database renameCollections fails if there is both a dropTarget and dropSource collection

Closed

is depended on by

SERVER-18310 Can't rollback dropCollection if new primary renamed the collection

Closed

is duplicated by

SERVER-28207 Recoverable Rollback: Support rolling back of renameCollection oplog entries using collection UUIDs.

Closed

is related to

SERVER-30212 Use two phase drop for renameCollection drops

Closed

Assignee:: Allison Chang (Inactive)

Reporter:: Allison Chang (Inactive)

Participants:: Allison Chang, Githook User

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: Jul 03 2017 03:33:19 PM UTC

Updated:: Oct 30 2023 11:15:31 PM UTC

Resolved:: Jul 31 2017 09:37:07 PM UTC

Confidence Status Last Update:: 05/Jul/17 3:15 PM

GA Target Date:: None

Public Preview Target Date:: None

Private Preview Target Date:: None

Experiment Target Date:: None

Details

Description

Attachments

Issue Links

Activity

People

Dates