[MXS-360] Persistent connections: maxadmin reports 0 all the time even if connections are created Created: 2015-09-10  Updated: 2015-12-01  Resolved: 2015-12-01

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: None
Fix Version/s: 1.3.0

Type: Bug Priority: Major
Reporter: Timofey Turenko Assignee: martin brampton (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Attachments: File maxscale.cnf.template.pers_01    

 Description   

Test:
1. create 40 connections to RW split router for Galera cluster
2. close connections
3. Check 'show servers' output

Result:

Server 0x3a45630 (gserver1)
Server: 10.105.147.3
Status: Master, Synced, Running
Protocol: MySQLBackend
Port: 3306
Server Version: 5.5.45-MariaDB-wsrep-log
Node Id: 0
Master Id: -1
Repl Depth: 0
Number of connections: 40
Current no. of conns: 40
Current no. of operations: 0
Persistent pool size: 0
Persistent measured pool size: 0
Persistent max size achieved: 0
Persistent pool size limit: 10
Persistent max time (secs): 3660

 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-09-10 ]

tturenkoHave you enabled persistent connections ? Have you set persistpoolmax to non-zero value in config file?

Comment by martin brampton (Inactive) [ 2015-09-10 ]

I'm not clear exactly what the test is here. A connection only enters the persistent connection pool when it has been closed and has features that would make it suitable for re-use.

Comment by Dipti Joshi (Inactive) [ 2015-09-10 ]

tturenko Please attach config file.

Comment by Timofey Turenko [ 2015-09-10 ]

I've added maxscale.cnf template

Comment by martin brampton (Inactive) [ 2015-09-10 ]

Sorry, I think you may be missing a piece of information. Changes were made to persistent connections as part of MXS-329 so the code to test against for persistent connections is currently the MXS-329 branch.

Comment by Johan Wikman [ 2015-09-14 ]

Is this repeatable with MXS-329?

Comment by Dipti Joshi (Inactive) [ 2015-11-24 ]

tturenko, martin brampton Since MXS-329 is merged with develop, have we retested this issue ? If we have, is this issue fixed ?

Comment by Timofey Turenko [ 2015-12-01 ]

alreadyfixed. closing

number of connections from maxadmin is correct a few seconds after connections creation, not immediately

Generated at Thu Feb 08 03:58:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.