Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71768

Have secondary nodes vote for the index build commit quorum if the index already exists

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03, Execution Team 2023-04-17, Execution Team 2023-05-29

      There have been several occurrences in Atlas where one or more secondary nodes already have an index built that the primary does not have. We think this is due to interrupted rolling index builds. Creating the same index on the primary may result in the index build stalling indefinitely as the secondary nodes with the index will return early and skip voting for the index's commit quorum.

      The workaround is to adjust the commit quorum using the setIndexCommitQuorum command.

      It would be ideal if secondary nodes with the index already existing could participate in voting for the commit quorum to avoid this.

            Assignee:
            yujin.kang@mongodb.com Yujin Kang Park
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: