hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix configuration guide documentation

Browse Source 
Fixed limitations section, the heading depths and the document name,
corrected localhost_match_wildcard_host, added deprecation notes where
required.
This commit is contained in:
Markus Mäkelä 2019-06-17 11:24:41 +03:00
parent dbc321cbbe
commit f9eef8f44c
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -1252,6 +1252,8 @@ _5.5.5-MaxScale-Service_ being sent to the client.
### `weightby`
**Note:** This parameter has been deprecated in MaxScale 2.3.2.
[A rank mechanism](https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Getting-Started/Configuration-Guide.md#rank)
will be added in MaxScale 2.4 to allow better control over server usage.
The weightby parameter is used in conjunction with server parameters in order to
control the load balancing applied in the router in use by the service. This
@ -1985,9 +1987,6 @@ password=61DD955512C39A4A8BC4BB1E5F116705
Read the following documents for different methods of altering the MaxScale
configuration at runtime.
* MaxAdmin
* [Runtime Configuration Changes](../Reference/MaxAdmin.md#runtime-configuration-changes)
* MaxCtrl
* [`create`](../Reference/MaxCtrl.md#create)
* [`destroy`](../Reference/MaxCtrl.md#destroy)
@ -1997,6 +1996,9 @@ configuration at runtime.
* [REST API](../REST-API/API.md) documentation
* MaxAdmin (deprecated)
* [Runtime Configuration Changes](../Reference/MaxAdmin.md#runtime-configuration-changes)
All changes to the configuration are persisted as individual configuration files
in `/var/lib/maxscale/maxscale.cnf.d/`. These files are applied after the main
configuration file and all auxiliary configurations have been loaded. This means