Merge branch 'develop' into MXS-129
This commit is contained in:
@ -1679,7 +1679,7 @@ Loaded 34 users.
|
||||
|
||||
## Reload config
|
||||
|
||||
The reload config command can be used to force MaxScale to re-read the MaxScale.cnf and update itself to the latest configuration defined in that configuration file. It is also possible to force the reading of the configuration file by sending a HangUp signal (SIGHUP) to the maxscale process.
|
||||
The reload config command can be used to force MaxScale to re-read the maxscale.cnf and update itself to the latest configuration defined in that configuration file. It is also possible to force the reading of the configuration file by sending a HangUp signal (SIGHUP) to the maxscale process.
|
||||
|
||||
**MaxScale>** reload config
|
||||
|
||||
@ -1789,7 +1789,7 @@ MariaDB Corporation MaxScale /home/jdoe/bin/develop/log/skygw_msg1.log Tue Dec
|
||||
|
||||
2014-12-09 14:47:05 Log directory : /home/jdoe/bin/develop/log
|
||||
|
||||
2014-12-09 14:47:05 Configuration file : /home/jdoe/bin/develop/etc/MaxScale.cnf
|
||||
2014-12-09 14:47:05 Configuration file : /home/jdoe/bin/develop/etc/maxscale.cnf
|
||||
|
||||
2014-12-09 14:47:05 Initialise CLI router module V1.0.0.
|
||||
|
||||
|
@ -15,7 +15,7 @@ name-value pairs.
|
||||
Routing queries to a server:
|
||||
-- maxscale route to [master | slave | server <server name>]
|
||||
|
||||
The name of the server is the same as in MaxScale.cnf
|
||||
The name of the server is the same as in maxscale.cnf
|
||||
|
||||
Creating a name-value pair:
|
||||
-- maxscale <param>=<value>
|
||||
|
@ -591,7 +591,7 @@ Some monitors provide a replication heartbeat mechanism that monitors the delay
|
||||
MaxScale> enable heartbeat "MySQL Monitor"
|
||||
MaxScale>
|
||||
|
||||
Please note that changes made via this interface will not persist across restarts of MaxScale. To make a permanent change edit the MaxScale.cnf file.
|
||||
Please note that changes made via this interface will not persist across restarts of MaxScale. To make a permanent change edit the maxscale.cnf file.
|
||||
|
||||
Enabling the replication heartbeat mechanism will add the display of heartbeat information in the show server output
|
||||
|
||||
@ -786,11 +786,11 @@ Two commands are provided to change the logging levels within MaxScale, disable
|
||||
MaxScale> disable log debug
|
||||
MaxScale>
|
||||
|
||||
Please note that changes made via this interface will not persist across restarts of MaxScale. To make a permanent change edit the MaxScale.cnf file.
|
||||
Please note that changes made via this interface will not persist across restarts of MaxScale. To make a permanent change edit the maxscale.cnf file.
|
||||
|
||||
## Reloading The Configuration
|
||||
|
||||
A command, reload config, is available that will cause MaxScale to reload the MaxScale.cnf configuration file.
|
||||
A command, reload config, is available that will cause MaxScale to reload the maxscale.cnf configuration file.
|
||||
|
||||
## Shutting Down MaxScale
|
||||
|
||||
@ -798,7 +798,7 @@ The MaxScale server may be shutdown using the shutdown maxscale command.
|
||||
|
||||
# Configuring MaxScale to Accept MaxAdmin Connections
|
||||
|
||||
In order to allow the use of the MaxAdmin client interface the service must be added to the MaxScale.cnf file of the Maxscale server. The CLI service itself must be added and a listener for the maxscaled protocol.
|
||||
In order to allow the use of the MaxAdmin client interface the service must be added to the maxscale.cnf file of the Maxscale server. The CLI service itself must be added and a listener for the maxscaled protocol.
|
||||
|
||||
The default entries required are shown below.
|
||||
|
||||
|
Reference in New Issue
Block a user