Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5809

Invariant failure: stable timestamp does not equal appliedThrough timestamp

    XMLWordPrintableJSON

Details

    • 5
    • Storage Engines 2020-03-23

    Description

      Below invariant failure was captured by 2 tests of noPassthrough task in a recent mongo 4.4 patch build:

      [js_test:timestamp_index_builds] 2020-03-10T05:50:19.806+0000 d21521| {"t":{"$date":"2020-03-10T05:50:19.806+0000"},"s":"F", "c":"-",       "id":23081,"ctx":"initandlisten","msg":"Invariant failure {expr} {msg} {file} {line}","attr":{"expr":"!stableTimestamp || stableTimestamp->isNull() || appliedThrough.isNull() || *stableTimestamp == appliedThrough.getTimestamp()","msg":"Stable timestamp Timestamp(1583819411, 1) does not equal appliedThrough timestamp { ts: Timestamp(1583819411, 2), t: 1 }","file":"src/mongo/db/repl/replication_recovery.cpp","line":429}}

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. WT-5780 Fix timestamp_index_build.js in noPassthrough suite.

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

          Improvement - An improvement or enhancement to an existing feature or task. WT-5814 Understand the behaviour of out of order timestamps

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

          Activity

            People

              chenhao.qu@mongodb.com Chenhao Qu
              luke.chen@mongodb.com Luke Chen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: