[MXS-364] Idle Client receives an error mysql has gone away after 10 minutes Created: 2015-09-15  Updated: 2016-10-10  Resolved: 2016-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.2.0
Fix Version/s: N/A

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

The MySQL backend is a Percona XtraDB Cluster with 3 nodes.
Maxscale has been installed using the debian package.
All the servers are running DEBIAN WHEEZY 7.8

Issue Links:
Duplicate
duplicates MXS-827 ReadWriteSplit only keeps used connec... Closed

 Description   

We are using a script that create an index on a large table. The script ends with an error saying "MySQL has gone away" after exactly 10 minutes.
From what we see in the network packet capture we made, the Maxscale server is sending a TCP FIN/ACK after 10 minutes of inactivity of the client.
The query to create the index is still running on the cluster after Maxscale has closed the connection with the client and ends correctly.
If we change the parameters of the script ot execute the query directly on the cluster without using Maxscale, everything is working properly.

 Comments   
Comment by markus makela [ 2016-02-04 ]

xlCan you try this with the 1.3.0-beta version of MaxScale? The packages can be found here: http://maxscale-jenkins.mariadb.com/ci-repository/1.3.0-beta-release1/mariadb-maxscale/

Comment by markus makela [ 2016-03-23 ]

Please try this with the 1.4.0-beta release of MaxScale. The packages are available on the portal.

Comment by markus makela [ 2016-05-08 ]

xlPlease try this out with the 1.4.3 release of MaxScale.

Comment by markus makela [ 2016-08-30 ]

This could be caused by the backend server closing the connection, see MXS-827.

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