[SERVER-54014] Define a reasonable maxTimeMsOverride for the checkOID requests Created: 25/Jan/21 Updated: 29/Oct/23 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.2.13, 4.4.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Alexandre Bique (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Sharding-EMEA, neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||
| Sprint: | Sharding 2021-02-08 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 9 | ||||||||
| Description |
|
The requests that we send from the Balancer thread from the primary node of the CSRS doen't have a reasonable time out: the opCtx of that thread doesn't define the maxTimeMs and, since we do not specify the maxTimeMsOverride it is set to Milliseconds::max(). The main problem is that if any of these requests cannot be fulfilled we will hang there forever. The goal of this ticket is to define a reasonable maxTimeMsOverride for those commands (30s). |
| Comments |
| Comment by Githook User [ 17/Feb/21 ] |
|
Author: {'name': 'Alexandre Bique', 'email': 'alexandre.bique@mongodb.com', 'username': 'abique'}Message: |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'Alexandre Bique', 'email': 'alexandre.bique@mongodb.com', 'username': 'abique'}Message: |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'Alexandre Bique', 'email': 'alexandre.bique@mongodb.com', 'username': 'abique'}Message: |