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

allow enableMajorityReadConcern=false to work

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • None
    • 3.6.1
    • Storage
    • None
    • Fully Compatible
    • Storage 2017-12-04, Storage 2017-12-18
    • 0

    Description

      Investigate the possibility of using this parameter to deactivate storing timestamps past the lastAppliedOpTime. That is, if this parameter was disabled, then instead of setting oldest_timestamp at the commit level, we would set it based on the lastAppliedOpTime.

      Attachments

        Issue Links

          depends on

          New Feature - A new feature of the product, which has yet to be developed. WT-3762 Allow the oldest_timestamp to be moved backwards.

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

          Task - A task that needs to be done. SERVER-31350 make enableMajorityReadConcern parameter a no-op

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

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

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

          Activity

            People

              daniel.gottlieb@mongodb.com Daniel Gottlieb
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: