[DOCS-12605] Configuration option storage.indexBuildRetry should either be omitted or say it doesn't work even on standalone in version 4.0 Created: 08/Apr/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.0 Required
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Sheila Doyle Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

Ref :SERVER-38705 and DOCS-12378 a

 

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.
 
The noIndexBuildRetry flag 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.

 

The documentation implies that in version 4.0 indexBuildRetry defaults to 1 and will cause index's which failed to build to be rebuilt on restart. However SERVER-38705 says that they were always discarded . The documentation should be updated to reflect the status of indexBuildRetry option in version 4.0

 

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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