[SERVER-50176] The shardVersion recovery task runs on a fixed-size executor Created: 07/Aug/20 Updated: 29/Oct/23 Resolved: 14/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2020-08-10, Sharding 2020-08-24 |
| Participants: |
| Description |
|
Currently, the shardVersion recovery task is scheduled on a fixed-size executor. What is worse, the "opportunistic recovery" task, which we spawn on step-up, runs on the same fixed-size executor and does a blocking wait for the shardVersion recovery to complete, which is this is deadlock-prone. The shardVersion recovery task must instead use the sharding unilimited size executor. |
| Comments |
| Comment by Githook User [ 14/Aug/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |