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

Running without journaling doesn't set all OpTimes (lastDurableOpTime)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.4, 3.3.2
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Epic Link:
    • Sprint:
      Repl 10 (02/19/16)

      Description

      This is currently breaking ReadConcern.Majority due to the commit optime not being updated correctly when you have a wired tiger primary without journaling enabled.

        Attachments

          Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-22488 Improve test coverage of new writeConcern j:true behavior

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22276 implement "j" flag in write concern apply to secondary as well as primary

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: