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

Change w:majority write concern to indicate a majority of voting nodes

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 2.7.8
    • Replication
    • None

    Description

      In systems with non-voting nodes, confirmed w:majority writes might in some circumstances still roll back. This is because rollback is precluded by ensuring that a majority of voting nodes are aware of the write, but w:majority in a system with a high ratio of non-voting to voting nodes might not ensure this.

      Conversely, on clusters with a high non-voting to voting ratio, w:majority is really too strong a requirement for committedness. Only the majority of the voting nodes need to respond, to be safe from rollback.

      The work of this ticket is to change the meaning of "w:majority" to indicate acceptance of a write from the majority of voting nodes. No built-in write concern will provide the old functionality.

      Attachments

        Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-15060 Raise maximum number of nodes in a replica set

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-14308 replace replsets/majority.js with c++ unit tests covering the same functionality

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-16357 Chunk migration pre-commit write concern should be configurable

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-16597 Warn if no voting data bearing members

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13070 Including arbiters when calculating replica set majority can break balancing / prevents fault-tolerant majority writes

          • Major - P3 - Major loss of function.
          • Closed
          tested by

          Task - A task that needs to be done. SERVER-15764 unit test new majority write behavior in ReplicationCoordinator

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              matt.dannenberg Matt Dannenberg
              schwerin@mongodb.com Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: