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

Race in OplogFetcherAutoReconnectsButFails

    XMLWordPrintableJSON

Details

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

    Description

      In test OplogFetcherAutoReconnectsButFails, the intention was to simulate a disconnect while the oplog fetcher is waiting for a response from the first find command and shut down the remote server before the oplog fetcher retries to connect. However, if _mockServer->shutdown() runs too fast, it could fail the initial connection as well, which is not what this test was intended for.

      Instead, we should use simulateNetworkDisconnect to simulate a disconnect then use the hangBeforeOplogFetcherRetries failpoint to hang the retry and shut down the remote server before the oplog fetcher retries.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: