[SERVER-30482] Mongos should not close sessions to below the configured ShardingTaskExecutorPoolMinSize Created: 02/Aug/17  Updated: 30/Oct/23  Resolved: 11/Oct/17

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 3.2.16
Fix Version/s: 3.2.18, 3.4.11, 3.6.0-rc0

Type: Bug Priority: Major - P3
Reporter: Andrew Young Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: neweng, platforms-interns-2017
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-10907 Docs for SERVER-30482: Mongos should ... Closed
Backwards Compatibility: Minor Change
Backport Requested:
v3.4, v3.2
Sprint: Platforms 2017-09-11, Platforms 2017-10-02, Platforms 2017-10-23
Participants:
Case:

 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 [ 01/Nov/17 ]

Author:

{'name': 'Henrik Edin', 'username': 'henrikedin', 'email': 'henrik.edin@mongodb.com'}

Message: SERVER-30482 Verify and enforce good ordering for the values for the sharding task executor refresh and host timeouts.

(cherry picked from commit 8c50e87a82afdb7852fbac32e9bb4dbe7b6f8030)
Branch: v3.2
https://github.com/mongodb/mongo/commit/577f6c2677eb1384e5a50b6829bfa2ad7665e3a1

Comment by Githook User [ 01/Nov/17 ]

Author:

{'name': 'Henrik Edin', 'username': 'henrikedin', 'email': 'henrik.edin@mongodb.com'}

Message: SERVER-30482 Verify and enforce good ordering for the values for the sharding task executor refresh and host timeouts.

(cherry picked from commit 8c50e87a82afdb7852fbac32e9bb4dbe7b6f8030)
Branch: v3.4
https://github.com/mongodb/mongo/commit/8e275be84c951475eb6405bc770b3be8a5d817fb

Comment by Githook User [ 11/Oct/17 ]

Author:

{'email': 'henrik.edin@mongodb.com', 'name': 'Henrik Edin', 'username': 'henrikedin'}

Message: SERVER-30482 Verify and enforce good ordering for the values for the sharding task executor refresh and host timeouts.
Branch: master
https://github.com/mongodb/mongo/commit/8c50e87a82afdb7852fbac32e9bb4dbe7b6f8030

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