[MXS-776] Documentation about limitations of reload config is not clear Created: 2016-06-21 Updated: 2016-07-06 Resolved: 2016-07-06 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core, Documentation, maxadmin |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | configuration, documentation | ||
| Sprint: | 2016-13 |
| Description |
|
The documentation about the limitations of reloading configuration dynamically is not very clear. For example, I've been told that it is probably not possible to change disable_sescmd_history dynamically, but there is no indication of that limitation or why that limitation exists on that page or this page: https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale/readwritesplit/ |
| Comments |
| Comment by markus makela [ 2016-07-06 ] |
|
The configuration documentation now states which parameters can be changed at runtime. Only generic parameters common to all services can be changed but there are a few exceptions, namely the readwritesplit parameters. |