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

It is possible for the oplogTruncateAfterPoint logic to fail to find a oplog entry w/ timestamp LTE WT's all_durable timestamp

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.7, 5.0.0-rc0
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2021-05-03, Execution Team 2021-05-17
    • 123

    Description

      It is possible for the oplogTruncateAfterPoint logic to fail to find a oplog entry w/ timestamp LTE WT's all_durable timestamp if the oplog truncation logic manages to delete older oplog entries very quickly. There is nothing stopping this behavior because there currently are no special rules to avoid truncating the oplog needed by the oplogTruncateAfterPoint logic in WiredTigerKVEngine::getPinnedOplog().

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: