[DOCS-12378] Docs for SERVER-38705: Remove the --noIndexBuildRetry server parameter flag and the storage.indexBuildRetry config file option Created: 18/Jan/19  Updated: 13/Nov/23  Resolved: 22/Jan/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.8, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-38705 Remove the --noIndexBuildRetry server... Closed
Duplicate
Related
related to DOCS-12380 Docs for SERVER-37270: Remove foregro... Closed
related to DOCS-12741 Docs for SERVER-40882: Return the --n... Closed
Participants:
Days since reply: 4 years, 36 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

1) The --noIndexBuildRetry server parameter flag was removed from the command line options.
2) In the mongod config file, we've removed the storage.indexBuildRetry option.

Engineering Ticket Description:

The command line noIndexBuildRetry flag will be removed in v4.2. Index builds cannot be arbitrarily aborted on a single replica set member with two-phase index builds in-progress. In v4.2 users will instead be able to abort in-progress index builds via killOp or dropIndexes against the primary. Slow startup due to waiting for index builds to finish will also no longer be of concern in v4.2 because startup will restart the index builds on separate threads and continue without waiting for them to finish (SERVER-37966).

Standalone mode nodes will neither recover nor discard any in-progress index builds if the node was previously a replica set member. The in-progress index builds will be ignored until the node is re-introduced to its replica set (SERVER-37637). In v4.0, standalone nodes always discarded all in-progress index builds, and an always standalone node restarted as standalone will continue to discard in-progress in v4.2. The noIndexBuildRetry flag therefore never had a use with standalone nodes in v4.0, and we do not want it to affect cross-replica set index builds present on standalones.

Scope of changes

  • index-creation (more to come regarding background and removal of foreground through other tickets)
  • configuration file (options and ref)
  • mongod file (options and ref)
  • 4.2-compatibility (and seealso to 4.2 rel notes)

Impact to Other Docs

opsmgr/cloud mgr link to the option

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 04/Jun/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12741: Revert "DOCS-12378: 4.2 remove --noIndexBuildRetry && storage.indexBuildRetry"

This reverts commit a17d34232929ca6ed7480b924332c2d94378b6f4.
Branch: master
https://github.com/mongodb/docs/commit/f0194962adcb06162a332953994fa357b427e2f0

Comment by Githook User [ 22/Jan/19 ]

Author:

{'email': 'kay.kim@mongodb.com', 'name': 'Kay Kim'}

Message: DOCS-12378: 4.2 remove --noIndexBuildRetry && storage.indexBuildRetry
Branch: master
https://github.com/mongodb/docs/commit/a17d34232929ca6ed7480b924332c2d94378b6f4

Generated at Thu Feb 08 08:05:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.