[MXS-3730] idle_session_pool_time=0s doesn't immediately pool idle connections Created: 2021-08-16  Updated: 2021-08-16  Resolved: 2021-08-16

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 6.1.1
Fix Version/s: 6.2.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

When configured with idle_session_pool_time=0s, the connections will only be put into the
pool once they have been idle longer than the configured time. Since the comparison is done at one second granularity, a connection would have to be idle for more than a second for it to be put into the pool.

The interpretation of the value should be changed to use greater-than-or-equal semantics instead of the current greater-than semantics. Additionally, the granularity can be changed to use the internal ticks of 100 milliseconds.


Generated at Thu Feb 08 04:23:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.