[MXS-3253] Maxscale uses half of my server memory Created: 2020-10-22  Updated: 2020-12-08  Resolved: 2020-12-08

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

Type: Bug Priority: Major
Reporter: steven lin Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Centos 7


Attachments: JPEG File Noname.jpg    
Issue Links:
Duplicate
duplicates MXS-3068 memory leak Closed
Sprint: MXS-SPRINT-120

 Description   

It's strange that Maxscale uses so much memory.
I didn't use cache of Maxscale.

[enode1]
type=server
address=192.168.0.158
port=3306
protocol=mariadbbackend
priority=2
 
[enode2]
type=server
address=192.168.0.159
port=3306
protocol=mariadbbackend
priority=1
 
[enode3]
type=server
address=192.168.0.160
port=3306
protocol=mariadbbackend
priority=3
 
[ESTORE_Monitor]
type=monitor
module=galeramon
servers=enode1,enode2,enode3
user=maxscale_monitor
password=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
monitor_interval=3000ms
use_priority=true
#disable_master_failback=true
 
[ESTORE_Service]
type=service
router=readwritesplit
#slave_selection_criteria=LEAST_CURRENT_OPERATIONS
slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS
servers=enode1,enode2,enode3
user=maxscale_monitor
password=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
enable_root_user=1
connection_timeout=1800s
max_connections=600
max_slave_connections=1
#filters=MaxScaleCache
log_auth_warnings=true
master_accept_reads=true
master_failure_mode=fail_on_write
master_reconnection=true
max_sescmd_history=1000
prune_sescmd_history=true
#disable_sescmd_history=true
 
[ESTORE_Listener]
type=listener
service=ESTORE_Service
protocol=mariadbclient
address=0.0.0.0
port=3308



 Comments   
Comment by markus makela [ 2020-10-30 ]

Does the amount of memory used change when you lower the value of max_sescmd_history to 50?

Comment by steven lin [ 2020-11-02 ]

No. It doesn't change if i lower the value.

Comment by markus makela [ 2020-12-08 ]

I'll close this as a duplicate of MXS-3068. Once we've fixed it, I assume this problem will go away as well.

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