Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11585

Mongos uses majority writeconcern for all metadata operations

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.7.3
    • Server
    • None
    • 0.5
    • KANBAN BUCKET
    • true

    Description

      Mongos now converts writeConcern of all metadata operations (create/drop/dropDatabase, etc.) to w: majority, per a comment in SERVER-33317. This should be documented.

      Scope of changes:

      • 4.0
      • 4.0-compatibility
      • sharded-cluster-query-router
      • movePrimary
      • create / db.createCollection
      • drop / db.collection.drop
      • dropDatabase cmd only as helper does not take write concern
      • shardCollection / sh.shardCollection
      • enableSharding
      • addShard
      • removeShard
        • remove-shards-from-cluster.txt

      Impact to other docs outside of this product:

      none

      MVP:

      Resources:

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33317 3.7 sharded clusters ignore create command write concern

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

          Task - A task that needs to be done. DOCS-11758 Docs for SERVER-34991: JS tests doing transaction operations must use majority writeConcern for drops

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

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              greg.mckeon@mongodb.com Gregory McKeon (Inactive)
              Jess Mokrzecki Jess Mokrzecki
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                4 years, 39 weeks ago