[DOCS-10907] Docs for SERVER-30482: Mongos should not close sessions to below the configured ShardingTaskExecutorPoolMinSize Created: 16/Oct/17  Updated: 13/Nov/23  Resolved: 06/Nov/17

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 3.6.0-rc0, 3.4.11, 3.2.18, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kevin Albertson
Resolution: Fixed Votes: 0
Labels: neweng, platforms-interns-2017
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-30482 Mongos should not close sessions to b... Closed
Participants:
Days since reply: 5 years, 8 weeks, 6 days ago
Epic Link: DOCS: 3.6 Server

 Description   

We document them in the https://docs.mongodb.com/manual/reference/parameters/index.html#param.ShardingTaskExecutorPoolHostTimeoutMS

Documentation Request Summary:

The server is now enforcing and correcting bad values of these parameters in the following way. If they are documented, the documentation should probably reflect this:

ShardingTaskExecutorPoolHostTimeoutMS > ShardingTaskExecutorPoolRefreshRequirementMS > ShardingTaskExecutorPoolRefreshTimeoutMS

ShardingTaskExecutorPoolHostTimeoutMS > ShardingTaskExecutorPoolRefreshRequirementMS + ShardingTaskExecutorPoolRefreshTimeoutMS

Engineering Ticket Description:

While doing some testing with mongos connection we noticed that if you set the ShardingTaskExecutorPoolHostTimeoutMS below the heartbeat timer mongos will close the idle sessions to secondaries (in our case they aren't in use).

This is a poor behavior because ShardingTaskExecutorPoolMinSize is set to 1, and this ShardingTaskExecutorPoolHostTimeoutMS enforcement is causing the only single connection open to close-- which means that mongos must then immediately create a new one.

Mongos should not close sessions to below the configured ShardingTaskExecutorPoolMinSize regardless of the configured ShardingTaskExecutorPoolHostTimeoutMS



 Comments   
Comment by Githook User [ 13/Dec/18 ]

Author:

{'username': 'kevinAlbs', 'email': 'kevin.albertson@10gen.com', 'name': 'Kevin Albertson'}

Message: DOCS-10907 add sharding parameter constraints
Branch: v3.4
https://github.com/mongodb/docs/commit/2b1e3954d9c43730c6ee35bac1ddcc45173238dd

Comment by Githook User [ 13/Dec/18 ]

Author:

{'username': 'kevinAlbs', 'email': 'kevin.albertson@10gen.com', 'name': 'Kevin Albertson'}

Message: DOCS-10907 add sharding parameter constraints
Branch: v3.2
https://github.com/mongodb/docs/commit/e828d5aa4dbcdefa074e36515c425a1a42fe3393

Comment by Githook User [ 06/Nov/17 ]

Author:

{'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@10gen.com'}

Message: DOCS-10907 add sharding parameter constraints
Branch: master
https://github.com/mongodb/docs/commit/0bd7497e7504996f472b02c2afa2757506f65c5c

Generated at Thu Feb 08 08:01:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.