[SERVER-29959] Fix renameCollection step in rollback via refetch Created: 03/Jul/17 Updated: 30/Oct/23 Resolved: 31/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | Backlog |
| Fix Version/s: | 3.5.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Chang | Assignee: | Allison Chang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 2017-07-31, Repl 2017-08-21 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 31/Jul/17 ] |
|
Author: {'email': 'allison.chang@10gen.com', 'username': 'archang68', 'name': 'Allison Chang'}Message: |