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

timestamp abort test failure lost a single record

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      The timestamp_abort program had a failure where it lost a single record. Job ran on margay.
      http://build.wiredtiger.com:8080/job/wiredtiger-test-recovery-stress/27680/

      Parent: compatibility: true, in-mem log sync: false, timestamp in use: true
Parent: Create 10 threads; sleep 19 seconds
CONFIG: test_timestamp_abort -C -h WT_TEST.timestamp-abort -T 10 -t 19
Kill child
Open database, run recovery and verify content
Got stable_val 1345263
records-0: COLLECTION no record with key 47699 record ts 467261 <= stable ts 1345263
records-0: COLLECTION error 0 absent records 47699-47699. Then keys 47700-143467 exist. Key range 0-143467
COLLECTION: 1 record(s) absent from 1407165

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: