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

Race between oplog visibility thread and timestamped inserts in dbtest repl

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-11-04
    • 0

      There was a race between the background WTOplogJournalThread and the test running inserts. The inserts set the WT transaction timestamp to Timestamp(1, 1) and that was why query_timestamp returned Timestamp(1, 0). SERVER-42497 added the setTimestamp call to the inserts.

      In production we don't have any logic that sets timestamps to anything other than what the LogicalClock timestamp generator gives us, so this race cannot occur in production. Ideally, no dbtest would explicitly set the timestamps backwards like this.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: