[SERVER-29747] Two phase drops: drop indexes before renaming collections if the rename will make the index name too long Created: 20/Jun/17 Updated: 30/Oct/23 Resolved: 17/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | William Schultz (Inactive) |
| 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 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
renameCollection will fail if it would cause an index name to be too long. To avoid this, we will drop any problematic indexes and log an oplog entry for their drops before renaming the collection and logging the collection drop to the oplog. This will only apply to mmap as we will relax this constraint for wiredTiger and mmap rollback will seamlessly succeed since we already know how to rollback index drops. |
| Comments |
| Comment by Githook User [ 25/Jul/17 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'}Message: |
| Comment by Githook User [ 17/Jul/17 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: |