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

Config replication and oplog commitment checks must only count voting nodes towards majority

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-03-09

      The config replication and oplog commitment safety checks during reconfig currently use the kConfigMajority write concern mode and a numeric write concern with the majority count of voting nodes. These mechanisms for satisfying write concern do not properly exclude non-voting nodes from the majority count. We should utilize the tag system (e.g. kInternalVoterTagName) to make these majority checks correctly exclude non-voting nodes. Javascript test repros of the bugs are attached.

            Assignee:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Reporter:
            william.schultz@mongodb.com Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: