Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14210

Fix atlas description of rolling indexes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Atlas
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      CET: Blondie (16-22 Feb 21)

      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.)

        Attachments

          Activity

            People

            Assignee:
            corry.root Corry Root
            Reporter:
            anton.oyung Anton Oyung
            Participants:
            Last commenter:
            Corry Root Corry Root
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              41 weeks, 2 days ago
              Date of 1st Reply: