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

Improve error message when users try to write to oplog before stable timestamp

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication

      Due to timestamping, it's not safe to write to the oplog with an entry ts field before the stable timestamp and WT will crash with the following. This is not obvious to the user what is wrong:

      [js_test:oplog_replay_on_startup] 2018-02-26T03:34:10.704+0000 d23260| 2018-02-26T03:34:10.703+0000 E STORAGE  [conn1] WiredTiger error (22) [1519616050:703015][79182:0x7f11d0adb700], WT_SESSION.timestamp_transaction: commit timestamp 3E800000001 older than stable timestamp 5a93803000000004: Invalid argument
[js_test:oplog_replay_on_startup] 2018-02-26T03:34:10.706+0000 d23260| 2018-02-26T03:34:10.703+0000 F -        [conn1] Fatal assertion 39001 BadValue: timestamp_transaction 22: Invalid argument at src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp 1157

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: