Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Gone away
-
None
-
None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
0
Description
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.
Attachments
Issue Links
- 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
-