Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
2.4.12
-
None
-
Centos 7
-
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
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-