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

Consider always decrementing NumAwaitingTopologyChanges after waiting in awaitHelloResponse

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Replication 2022-01-24, Replication 2022-02-07, Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21

      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.

            Assignee:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: