[SERVER-31990] Rollback can abort on long collection names. Created: 15/Nov/17 Updated: 30/Oct/23 Resolved: 29/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.6.0-rc4 |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | rbfz | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Repl 2018-01-01 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Here's a sequence of operations that seems to cause rollback to abort: Rollback seems to do the rename without dropping indexes, causing the rename back to the long name to fail when the index is present.
|
| Comments |
| Comment by Githook User [ 05/Dec/17 ] |
|
Author: {'username': 'judahschvimer', 'email': 'judah@mongodb.com', 'name': 'Judah Schvimer'}Message: (cherry picked from commit d923a5575bf277bfc49073597ca0c4d156b93492) |
| Comment by Githook User [ 29/Nov/17 ] |
|
Author: {'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}Message: |
| Comment by Robert Guo (Inactive) [ 15/Nov/17 ] |
|
Spencer This is indeed on WT, but we check the NS length as part of the renameCollection command, independent of the storage engine. |
| Comment by Spencer Brody (Inactive) [ 15/Nov/17 ] |
|
Is this on wiredTiger? My understanding was that WT doesn't have a character limit on collection or index names? |
| Comment by Judah Schvimer [ 15/Nov/17 ] |
|
If we hadn't fasserted we would have dropped the index shortly after. It should be safe to drop indexes by UUID first during rollback to fix this. |