Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
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

Node A's oplog:
optime 1: dropCollection foo

Node B's oplog:
optime 1': renameCollection foo -> bar

When node A enters rollback it will try to "undo" the dropCollection by resyncing the foo collection from node B. But node B won't have any foo collection anymore since it has been renamed to bar. This will cause the nodes to silently be out of sync.

depends on

SERVER-29959 Fix renameCollection step in rollback via refetch

Closed

duplicates

SERVER-4941 collection rename may not replicate / clone properly during initial sync

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Mathias Stearn
Participants:: [DO NOT USE] Backlog - Replication Team, Eric Milkie, Judah Schvimer, Mathias Stearn
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: May 04 2015 05:52:19 PM UTC
Updated:: Dec 06 2022 04:52:14 AM UTC
Resolved:: Nov 15 2017 09:05:32 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates