[SERVER-62082] Consider always decrementing NumAwaitingTopologyChanges after waiting in awaitHelloResponse Created: 15/Dec/21 Updated: 29/Oct/23 Resolved: 13/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Replication 2022-01-24, Replication 2022-02-07, Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| 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. |
| Comments |
| Comment by Githook User [ 12/Mar/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |