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

Reintroduce enableMajorityReadConcern:false server parameter

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.3
    • Replication
    • Fully Compatible
    • Repl 2018-09-10, Repl 2018-09-24, Repl 2018-10-08
    • 0

    Description

      The enableMajorityReadConcern:false option exists on 3.6, to allow the server to avoid holding on to all history since the majority commit point. We would like to add this option on 4.0 to address pain due to commit point lag in replica sets with arbiters.

      This work should include adding the enableMajorityReadConcern:false Evergreen variant to 4.0, which was introduced in SERVER-36083. This variant should include all of transactions tests on 4.0.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-36985 Test single replica set transactions immediately after a rollbackViaRefetch

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-12081 Docs for SERVER-36982: Reintroduce enableMajorityReadConcern:false server parameter

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

          Task - A task that needs to be done. SERVER-32022 allow enableMajorityReadConcern=false to work

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: