# MaxScale documentation on GitHub:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Documentation-Contents.md
# Global parameters
#
# Complete list of configuration options:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Getting-Started/Configuration-Guide.md
[maxscale]
threads=1
# Server definitions
#
# Set the address of the server to the network
# address of a MySQL server.
#
[master]
type=server
address=10.0.0.208
port=3306
protocol=MySQLBackend
[master2]
type=server
address=10.0.0.221
port=3306
protocol=MySQLBackend
[master3]
type=server
address=10.0.0.209
port=3306
protocol=MySQLBackend
# Monitor for the servers
#
# This will keep MaxScale aware of the state of the servers.
# MySQL Monitor documentation:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Monitors/MySQL-Monitor.md
[MySQL Monitor]
type=monitor
module=galeramon
servers=master,master2,master3
user=root
passwd=test
monitor_interval=10000
# Service definitions
#
# Service Definition for a read-only service and
# a read/write splitting service.
#
# ReadConnRoute documentation:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Routers/ReadConnRoute.md
# ReadWriteSplit documentation:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Routers/ReadWriteSplit.md
[RW-Service]
type=service
router=readwritesplit
servers=master,master2,master3
user=root
passwd=test
max_slave_connections=100%
# This service enables the use of the MaxAdmin interface
# MaxScale administration guide:
# https://github.com/mariadb-corporation/MaxScale/blob/2.1/Documentation/Reference/MaxAdmin.md
# Listener definitions for the services
#
# These listeners represent the ports the
# services will listen on.
#
[Write-Listener]
type=listener
service=RW-Service
port=4306
protocol=MySQLClient
#socket=/tmp/rwsplit.sock
[MaxAdmin]
type=service
router=cli
[MaxAdmin Unix Listener]
type=listener
service=MaxAdmin
protocol=maxscaled
socket=default
[MaxAdmin Inet Listener]
type=listener
service=MaxAdmin
protocol=maxscaled
address=localhost
port=6603Hi,
The reload config command is deprecated and never worked
correctly. We recommend using the runtime configuration commands
added to MaxAdmin in MaxScale 2.1. For more information, you can
read this document:
https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale-21-maxadmin-admin-interface/#runtime-configuration-changes
Markus
--
You received this message because you are subscribed to the Google Groups "MaxScale" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maxscale+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Markus Mäkelä, Software Engineer MariaDB Corporation t: +358 40 7740484 | Skype: markus.j.makela
Hi,
I think that behavior is caused by the reload config and restarting MaxScale should fix it.
Markus
Any runtime configuration changes to servers are persisted meaning that they will still be in effect even after a restart
Hi,
The configurations made at runtime are saved into a file (you can find these in /var/lib/maxscale/maxscale.cnf.d/) which makes the changes persistent. The original configuration file is not modified since MaxScale rarely has write access to its own configuration file.
Starting with MaxScale 2.1, you can sync configuration files by
using rsync on the persisted configuration file directory
/var/lib/maxscale/maxscale.cnf.d/ and then copy the original
configuration file. This should allow you to duplicate a running
MaxScale setup on another server.
Markus