[MXS-3144] connection_timeout at service section Created: 2020-08-28  Updated: 2020-08-31  Resolved: 2020-08-28

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

Type: Bug Priority: Major
Reporter: febriyant Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: timeout
Environment:

Centos 7


 Description   

i have configuration service on maxscale like this 

[Read-Write-Service-Name]
 
...
 
connection_timeout=120
 
...

this mean if from client processing query and still running more than 120 seconds will be kill the connection ?
OR
this is mean if from client processing query and still running or query is complete but data still processing fetch to client more than 120 seconds connection will be kill ?

 Comments   
Comment by markus makela [ 2020-08-28 ]

This is for any period of idleness that exceeds the configured value. This means that whether a query runs for 120 seconds or a client is idle for 120 seconds, the connection will be closed. The parameter behaves more like wait_timeout in MariaDB than a regular network timeout.

Comment by febriyant [ 2020-08-31 ]

so whats you mean is maxscale will be not check about activity from client. if client idle or runs query more than 120 seconds the connection will be closed ?

Comment by markus makela [ 2020-08-31 ]

Yes, that is correct.

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