[SERVER-39022] Make the sharding fixed task executor use unlimited thread pool size Created: 15/Jan/19 Updated: 29/Oct/23 Resolved: 16/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Improvement | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-01-28 |
| Participants: |
| Description |
|
Currently, the fixed sharding task executor is built on top of NetworkInterfaceThreadPool, which only uses a single ASIO thread or the caller's thread. This makes it unsuitable for scheduling more than one operation on it or for scheduling anything blocking. We should bump the size of this pool to infinite and make it use a regular ThreadPool. |
| Comments |
| Comment by Githook User [ 16/Jan/19 ] |
|
Author: {'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev'}Message: |