Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.3.4, 2.3.5
-
None
-
CentOS 7 / Kernel 4.4.169 / MariaDB 10.3.13 galera
Description
After we upgraded from 2.2.x to 2.3.x and moved our production cluster to this version maxscale keeps increasing it's memory usage until reaches 100% (we didn't let it OOM due to the production nature). Our configuration is as follows:
type=service
|
router=readwritesplit
|
servers=db1,db2,db3
|
connection_keepalive=30
|
max_sescmd_history=0
|
disable_sescmd_history=true
|
master_accept_reads=false
|
master_failure_mode=fail_on_write
|
enable_root_user=true
|
master_reconnection=false
|
prune_sescmd_history=true
|
causal_reads=true
|
causal_reads_timeout=2
|
What is the best way to debug this further? We handle about 2000 qps with a mix of short and long lived sessions