[DOCS-14210] Fix atlas description of rolling indexes Created: 10/Feb/21  Updated: 29/Oct/23  Resolved: 18/Feb/21

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Anton Oyung Assignee: Corry Root
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 2 years, 50 weeks, 6 days ago
Story Points: 2

 Description   

Description

The current description for[ rolling indexes |https://docs.atlas.mongodb.com/data-explorer/indexes/#optional-enable-building-indexes-in-a-rolling-fashion] does not clearly explain the behavior, since one node is removed at a time but multiple nodes can be down at once. 
 
Original text 

Building indexes in a rolling fashion reduces the performance impact of building indexes on replica sets and sharded clusters. To maintain cluster availability, Atlas removes one node from the cluster at a time starting with a secondary.

Please update the description to be something to the effect of:

Building indexes in a rolling fashion reduces the performance impact of building indexes on replica sets and sharded clusters. To maintain cluster availability, Atlas removes one node from the cluster at a time starting with a secondary and maintaining a majority of nodes online at all times.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Corry Root [ 18/Feb/21 ]

anton.oyung, I broke the original text into a new format and added a bullet to clarify that Atlas keeps a majority of nodes online when you build indexes in a rolling fashion.

STAGE

BUILD

Comment by Corry Root [ 18/Feb/21 ]

nathan.contino, I broke the original text into a new format and added a bullet to clarify that Atlas keeps a majority of nodes online when you build indexes in a rolling fashion.

STAGE

BUILD

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