[MXS-3474] Strange persistent pool connection stats Created: 2021-03-31  Updated: 2021-08-13  Resolved: 2021-08-04

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbbackend
Affects Version/s: 2.5.9
Fix Version/s: 2.5.15

Type: Bug Priority: Minor
Reporter: Tim Westervoorde Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux 4.4.241-1.el7.elrepo.x86_64 CentOS 7
10.4.18-MariaDB MariaDB Server
MaxScale 2.5.9

Sprint: MXS-SPRINT-137

 Description   

connection_pool_empty 41540154
connections 1444
max_connections 2091
max_pool_size 13
persistent_connections 100
reused_connections 17979572

how can max_pool_size < persistent_connections ?



 Comments   
Comment by markus makela [ 2021-08-02 ]

I think this is a bug in the maximum value calculation where it doesn't do the comparisons correctly.

Comment by markus makela [ 2021-08-02 ]

Looks like the value was compared to the local pool of the thread instead of the sum of all pools for that server. The real maximum can be derived from the current buggy value by multiplying it with the number of threads in MaxScale.

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