[SERVER-18310] Can't rollback dropCollection if new primary renamed the collection Created: 04/May/15 Updated: 06/Dec/22 Resolved: 15/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
Node A's oplog: Node B's oplog: 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. |
| Comments |
| Comment by Judah Schvimer [ 15/Nov/17 ] |
|
This was fixed by the "Safe Rollback" project (PM-842) in |
| Comment by Eric Milkie [ 26/Aug/15 ] |
|
I believe this is a problem for any op in the renamed collection that needs to be rolled back, not just dropCollection. Using idents to uniquely identify collections instead of names will solve this. |