[SERVER-31091] The config server balancer stop command does not obey maxTimeMS Created: 14/Sep/17 Updated: 30/Oct/23 Resolved: 18/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.9, 3.5.13 |
| Fix Version/s: | 3.4.10, 3.6.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| 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 | ||||||||
| Backport Requested: |
v3.4
|
||||||||
| Sprint: | Sharding 2017-10-23 | ||||||||
| Participants: | |||||||||
| Description |
|
The config server side of the balancerStop command does not obey maxTimeMS and because of this can remain running even though the mongos side has timed out earlier. For longer-running balancer rounds this can lead to many threads getting stuck on the config server. |
| Comments |
| Comment by Githook User [ 18/Oct/17 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: (cherry picked from commit 689e308e910b1c689246da34ac85ca0198f68e4a) |
| Comment by Githook User [ 18/Oct/17 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |