[MXS-2500] connection keep alive still closing and idle detected Created: 2019-05-22  Updated: 2019-12-09  Resolved: 2019-12-09

Status: Closed
Project: MariaDB MaxScale
Component/s: Monitor
Affects Version/s: 2.3.7
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Stephane Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

centos 6.7

Issue Links:
Problem/Incident
is caused by MXS-2505 connection_keepalive independent from... Closed

 Description   

Hello,

On a read/write split service, I have this error log:
Lost connection to the master server, closing session. Lost connection to master server while connection was idle. Connection has been idle for 399.6 seconds. Error caused by: #HY000: Lost connection to backend server

on our mariadb server, the wait_timeout is set at 400 , if I change that value, the maxscale log error changes too.

in the maxscale.conf, I have: connection_keepalive=40 under the service section.

why do I have this lost connection to backend server, the connection_keepalive is supposed to keep it alive even if idle ?

thanks in advance

 Comments   
Comment by markus makela [ 2019-05-22 ]

Are the connections completely idle or do they simply perform SELECT statements for extended periods of time? The connection keepalive is intended to help with the case where the master is idle but the slaves are not.

Comment by Stephane [ 2019-05-22 ]

connections are not idle, master and slave are both performing select .
avg queries/seconds are between 150 and 300 .

Comment by markus makela [ 2019-05-22 ]

Are you using a connection pool of some sort? If you are, it could be that the connection pool keeps the connections in it for longer than 400 seconds.

Comment by Stephane [ 2019-05-22 ]

no, only 'simple' php / mysqi application that connects to the maxscale

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