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

Commit quorum value can get lost when the node gets restarted or rolled back.

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc2, 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-03-23, Execution Team 2020-04-06, Execution Team 2020-04-20
    • 50

      Currently, we persist the 'commitQuorum' value that user provided for createIndexes cmd, into "config.system.IndexBuilds collection, only on receiving first ready to commit vote by primary. If current primary gets restarted/rolled back before receiving any votes, and gets re-elected, then new primary would not know about the commit quorum value. Currently, we crash our system. As, our current contract is, two phase index build should have a commit quorum value set.

      To be noted, all the nodes who are eligible to become primary should have the commit quorum value, as the 2 phase index build can survive state transition and any node can act as coordinator for the 2 phase index build.

            Assignee:
            suganthi.mani@mongodb.com Suganthi Mani
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: