Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.0
-
Component/s: Core, Documentation, maxadmin
-
Labels:
-
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/