[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: SERVER-31723 limit mongod sharding exec pool to 1

The mongod sharding task executor pool (for arbitrary tasks) isn't
needed for user operations. As such, it should be limited to 1 pool,
rather than wasteful default (4 <= NCORES <= 64).
Branch: master
https://github.com/mongodb/mongo/commit/a40f9d9722555f53b390202f0dad508d6b7125d7

Generated at Thu Feb 08 04:28:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.