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

Reorder the history store inserts if there exists an update with same timestamp after restart

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc10, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage - Ra 2020-06-15, Storage - Ra 2020-06-29

      With the changes of WT-6349 of disabling checkpoints to clean the obsolete records from the data store, we identified a mismatch in applying the oplog with the stable timestamp.

      [js_test:rollback_test-6a49-1591065947633-0] 2020-06-09T13:02:00.927+0000 d20031| {"t":{"$date":"2020-06-09T13:02:00.927+00:00"},"s":"F",  "c":"-",        "id":23081,   "ctx":"initandlisten","msg":"Invariant failure","attr":{"expr":"!stableTimestamp || stableTimestamp->isNull() || appliedThrough.isNull() || *stableTimestamp == appliedThrough.getTimestamp()","msg":"Stable timestamp Timestamp(1591707670, 6) does not equal appliedThrough timestamp { ts: Timestamp(1591707670, 5), t: 7 }","file":"src/mongo/db/repl/replication_recovery.cpp","line":434}}
      [js_test:rollback_test-6a49-1591065947633-0] 2020-06-09T13:02:00.928+0000 d20031| {"t":{"$date":"2020-06-09T13:02:00.927+00:00"},"s":"F",  "c":"-",        "id":23082,   "ctx":"initandlisten","msg":"\n\n***aborting after invariant() failure\n\n"}
      

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: