[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:
Depends
is depended on by SERVER-37952 Restart index builds from persisted r... Closed
Related
related to SERVER-38351 Clear _unfinishedIndexes from IndexCa... Closed
related to SERVER-44206 Complete TODO listed in SERVER-37952 Closed
is related to SERVER-40883 Remove the --noIndexBuildRetry server... Closed
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: SERVER-39003 Do not drop index build interceptor and constraint violations tables on restart
Branch: master
https://github.com/mongodb/mongo/commit/33b153224e08a213f505c4f9e85d087d713cae5a

Generated at Thu Feb 08 04:50:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.