[SERVER-38351] Clear _unfinishedIndexes from IndexCatalog when restarting replica set member in standalone mode, without clearing persisted data Created: 30/Nov/18  Updated: 29/Jan/20  Resolved: 29/Jan/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Louis Williams
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38714 Standalone replica set nodes with unf... Closed
Duplicate
duplicates SERVER-37637 Standalone mode nodes should ignore i... Closed
Related
is related to SERVER-39003 Index build constraint violations and... Closed
is related to SERVER-38797 Add unit tests for the IndexCatalog Closed
Sprint: Storage NYC 2018-12-17, Storage NYC 2018-12-31, Storage NYC 2019-01-14, Execution Team 2020-02-10
Participants:

 Description   

This also must add a means of allowing createIndexes to request building an index that was cleared from the _unfinishedIndexes vector on startup.

This means adding either a new code path that handles discovering an existing persisted catalog entry for the newly requested index, or modifying the existing one somehow. Probably the easiest action is to clear the persisted state and restart the index build from the beginning.



 Comments   
Comment by Louis Williams [ 29/Jan/20 ]

This is mostly gone away, but the remainder of the work for this ticket will be done inĀ SERVER-37637.

Comment by Benety Goh [ 23/Jan/20 ]

Recent work that added the buildUUID to the index catalog for restarting index builds might affect the scope of this ticket.

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