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

Test (and possibly fix) behavior around majority commit point and oplog truncation

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.3, 4.1.1
    • Replication, Storage
    • Fully Compatible
    • v4.0
    • Storage NYC 2018-06-04, Storage NYC 2018-06-18, Storage NYC 2018-07-02

    Description

      First step here is that we need to add a js test for the behavior when replication majority commit point stops the oplog being truncated.

      Depending on what that test turns up, there might be follow-on work to improve that behavior.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. TOOLS-1993 TOOLS qa-tests failing on server unstable

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

          Bug - A problem which impairs or prevents the functions of the product. TOOLS-2027 mongostat qa-tests failing on server unstable

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29213 Have KVWiredTigerEngine implement StorageEngine::recoverToStableTimestamp

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

          Task - A task that needs to be done. SERVER-35747 Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp

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

          Activity

            People

              maria.vankeulen@mongodb.com Maria van Keulen
              ian@mongodb.com Ian Whalen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: