[SERVER-29770] Setting taskExecutorPoolSize server parameter at runtime should error Created: 21/Jun/17  Updated: 25/Jan/19  Resolved: 25/Jan/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Benjamin Caimano (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-38920 Allow ShardingTaskExecutorPool parame... Closed
Operating System: ALL
Sprint: Service Arch 2018-12-31, Service Arch 2019-01-14, Service Arch 2019-01-28, Service Arch 2019-02-11
Participants:

 Description   

Using the setParameter command to set taskExecutorPoolSize reports no error, but ithe value is ignored. The documentation suggests, this value can't be changed using the database command.

This occurs because in task_executor_pool.cpp, we define the parameter as follows:

MONGO_EXPORT_SERVER_PARAMETER(taskExecutorPoolSize, int, 0);

But it should be defined as

MONGO_EXPORT_STARTUP_SERVER_PARAMETER(taskExecutorPoolSize, int, 0);



 Comments   
Comment by Benjamin Caimano (Inactive) [ 25/Jan/19 ]

Closing because these parameters will be settable in the near future.

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