[SERVER-39003] Index build constraint violations and interceptor side table must not be dropped on server restart Created: 15/Jan/19 Updated: 29/Oct/23 Resolved: 06/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Louis Williams |
| 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: | Storage NYC 2019-01-28, Storage NYC 2019-02-11 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Standalone node and --repair behavior must be considered here. There are some cases where index builds are discarded/cleared, without starting up a MultiIndexBlock, and the tables must be cleared, too. We might not have a use case implemented yet, but there will be and it would be good to add the functionality here so that it is ready to use. Perhaps extend the logic that clears in-progress builds' persisted state. |
| Comments |
| Comment by Githook User [ 06/Feb/19 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |