[SERVER-41155] Allow noIndexBuildRetry and storage.indexBuildRetry options to drop unfinished indexes on replica set members Created: 15/May/19  Updated: 19/Jun/19  Resolved: 19/Jun/19

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Eric Milkie
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-40882 Return the --noIndexBuildRetry server... Closed
Sprint: Execution Team 2019-06-03, Execution Team 2019-06-17, Execution Team 2019-07-01
Participants:

 Description   

This could be done during ident reconciliation on startup. We could treat backgroundSecondary:true index builds like backgroundSecondary:false index builds, and discard (delete) them.

We would want this in v4.2 and v4.0 only – I hear v3.6 and earlier allow the noIndexBuildRetry and storage.IndexBuildRetry options to function on replica set members?



 Comments   
Comment by Eric Milkie [ 19/Jun/19 ]

I have decided we don't critically need this functionality at this time, as it would only be for rare situations.

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