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

applyOps to config rs does not wait for majority

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.1, 3.3.0
    • Fix Version/s: 3.2.3, 3.3.2
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding F (01/29/16), Sharding 10 (02/19/16)

      Description

      All applyOps and writes to config replica sets should have a write concern of 

      { w: 'majority', j: true }

      .

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-7637 Commands that take a writeConcern

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

          Improvement - An improvement or enhancement to an existing feature or task. DOCS-7079 applyOps takes a writeConcern

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22269 ReadConcern: majority does not reflect journaled state on PRIMARY

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

          Task - A task that needs to be done. SERVER-22846 Add applyOps command to readConcern passthrough

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: