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

Race in ExhaustCursorUpdatesLastKnownCommittedOpTime integration test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-02-10
    • 5

    Description

      There is a race between how the curOpMatch was generated and the queryCursor receiving a new batch from getMore. When the cursor receives a new batch, it sets the cursorId to 0 before parsing the response. So it is possible for the test thread to race with the queryThread and get a wrong cursorId 0. Therefore, it is possible for a test to use a wrong curOpMatch {command.getMore: 0} in confirmCurrentOpContents, resulting in test failures.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: