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

Consider always decrementing NumAwaitingTopologyChanges after waiting in awaitHelloResponse

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • Replication 2022-01-24, Replication 2022-02-07, Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21

    Description

      We currently only decrement on exceedTimeLimit errors in mongod and mongos. However it is possible for other types of error to occur (like MaxTimeMSExceeded) and we should just always decrement the counter since the thread is no longer waiting.

      Attachments

        Activity

          People

            vesselina.ratcheva@mongodb.com Vesselina Ratcheva
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: