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

Default write concern based on configuration (w:default)

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None

      Description

      Have a new write concern w:default, which is based on the configuration. Drives would specify this and the server would determine what this means. Having a default write concern that is concrete forces w:1 to account for standalones. This would allow for a more intuitive write concern depending on the MongoDB configuration (not the current state of that configuration).

      w:default would translate to:

      Standalone w:1
      Replica set w/ arbiter w:1
      Replica set w/o arbiter w:majority

      The argument could be made for Replica w/ arbiter to be half of the number of data bearing nodes as this is static with config too.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: