[SERVER-38571] Restarting a replica set member as a standalone should not discard !isBackgroundSecondaryBuild in-progress builds when it is a simultaneous index build Created: 12/Dec/18  Updated: 27/Oct/23  Resolved: 03/Feb/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: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-37952 Restart index builds from persisted r... Closed
Sprint: Execution Team 2020-02-24
Participants:

 Description   

along the lines of when twoPhaseIndexBuild is set to true, ignore isBackgroundSecondaryBuild for discarding purposes. Only discard single phase builds when isBackgroundSecondaryBuild is false.

Replica set member restart should act similarly.



 Comments   
Comment by Louis Williams [ 03/Feb/20 ]

This is done by SERVER-39451 and SERVER-44467.

Comment by Dianna Hohensee (Inactive) [ 30/Jan/19 ]

This seems to be part of the SERVER-37952 story, needed in order to get recovering index builds up and running.

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