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

mongos and configsvr get/setDefaultRWConcern commands

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding 2019-12-16, Sharding 2019-12-30
    • 16

      On MongoS:

      • setDefaultRWConcern - passes through to the same command on the config server
      • getDefaultRWConcern - passes through to the same command on the config server by default; if inMemory requested, then returns the locally cached value

      On Config Server or Plain Replica Set (not a shard):

      • setDefaultRWConcern - persists to disk
      • getDefaultRWConcern - by default returns what's persisted on disk; if inMemory requested, then returns the locally cached value

      On Shards:

      • setDefaultRWConcern - should error, because it must never be called directly
      • getDefaultRWConcern - should error, because it must never be called directly

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: