[SERVER-54504] Disable taskExecutorPoolSize for Linux Created: 12/Feb/21  Updated: 29/Oct/23  Resolved: 15/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Shameek Ray Assignee: Celina Tala
Resolution: Fixed Votes: 0
Labels: sa-remove-fv-backlog-22, save-for-celina
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-15632 Investigate changes in SERVER-54504: ... Closed
Duplicate
is duplicated by SERVER-77539 Mongos Performance Issue Closed
Problem/Incident
Related
related to SERVER-69755 Add taskExecutorPoolSize parameter te... Backlog
is related to SERVER-53899 TaskExecutor CPU fills up instantly Closed
is related to DOCS-16260 Update taskExecutorPoolSize Documenta... Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Sprint: Service Arch 2022-09-19
Participants:
Case:
Linked BF Score: 67
Story Points: 2

 Description   

This option is not useful for linux machines running 4.2 and beyond (and can cause problems if changed past the default of 1). So, we must disable this option for linux machines (It is always a value of 1). 

This parameter will still be available for Windows & OS X since we have found that it is useful for those machines, and that there are a non-trivial number of clusters running Windows in production.

Acceptance Criteria:

Customers can no longer change this parameter on linux machines.



 Comments   
Comment by Githook User [ 14/Sep/22 ]

Author:

{'name': 'Celina Tala', 'email': 'celinahtala@gmail.com', 'username': 'celinatala-1'}

Message: SERVER-54504 removed taskExecutorPoolSize for linux platform
Branch: master
https://github.com/mongodb/mongo/commit/f442d5df571f870219bb0d681c4b01245835c2b0

Comment by Celina Tala [ 06/Sep/22 ]

shameek.ray@mongodb.com Currently the solution is to remove the parameter on linux so the server will show an error message if the user attempts to set the parameter. Is that acceptable? 

Generated at Thu Feb 08 05:33:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.