[SERVER-31723] Ensure that mongod does not start up numCores task executors for sharding code Created: 25/Oct/17 Updated: 30/Oct/23 Resolved: 07/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 2017-11-13 |
| Participants: |
| Description |
|
As part of the logical sessions project, mongod was given the capability to read to and write from sharded collections. In mongos, we use a large number of task executors to back the traffic for these operations. Ensure that we have a sane, scaled-back solution for mongod. |
| Comments |
| Comment by Githook User [ 07/Nov/17 ] |
|
Author: {'name': 'Jason Carey', 'username': 'hanumantmk', 'email': 'jcarey@argv.me'}Message: The mongod sharding task executor pool (for arbitrary tasks) isn't |