[MXS-1366] Abrupt disconnections with persistent connections Created: 2017-08-21  Updated: 2020-08-25  Resolved: 2017-08-21

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.1.6
Fix Version/s: 2.1.7

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


 Description   

Repeated, short-lived sessions that execute short queries appear to trigger unexpected disconnections.
Initial analysis seems to suggest that the backend protocol receives an unexpected response to the COM_CHANGE_USER command. Ignoring this unexpected response and waiting for the actual response seems to treat the symptoms but the true cause is still unknown.

 Comments   
Comment by markus makela [ 2017-08-21 ]

When a session is stopped in a controlled fashion, the backend connections are very likely to be idle. This gives an extra qualification that must be met by all connections that are put into the pool.

Comment by markus makela [ 2017-08-21 ]

The connection must now be closed by a COM_QUIT to qualify for the connection pool. This will prevent most of the cases where a pooled connection is in an unexpected state.

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