[SERVER-37555] An abort of collMod need not refreshEntry for an index on rollback Created: 10/Oct/18 Updated: 29/Oct/23 Resolved: 15/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog |
| Affects Version/s: | 4.1.3 |
| Fix Version/s: | 4.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Neha Khatri | Assignee: | Neha Khatri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Storage Engines 2018-10-22 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 45 | ||||||||||||
| Story Points: | 3 | ||||||||||||
| Description |
|
When a collMod operation aborts its WriteUnitOfWork, it need not call refreshEntry on rollback. An index catalog change via collMod already invoke refreshEntry. The refreshEntry itself should restore its state on rollback as it registers an IndexRemoveChange to do that. |
| Comments |
| Comment by Githook User [ 16/Oct/18 ] | |||||||||||||||||
|
Author: {'name': 'nehakhatri5', 'email': 'neha.khatri@mongodb.com', 'username': 'nehakhatri5'}Message: | |||||||||||||||||
| Comment by Githook User [ 15/Oct/18 ] | |||||||||||||||||
|
Author: {'name': 'nehakhatri5', 'email': 'neha.khatri@mongodb.com', 'username': 'nehakhatri5'}Message: | |||||||||||||||||
| Comment by Neha Khatri [ 12/Oct/18 ] | |||||||||||||||||
|
I am able to reproduce the problem with following test and a uassert after the index update logic in collMod.
|