[MXS-2417] MaxScale main config should take precedence over runtime config on restart Created: 2019-04-02 Updated: 2021-05-06 Resolved: 2019-04-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.2.19 |
| Fix Version/s: | 2.3.6 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Muhammad Irfan | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently, MaxScale configuration (maxscale.cnf) reads AFTER runtime configuration (Mysql-Monitor.cnf). |
| Comments |
| Comment by Geoff Montee (Inactive) [ 2019-04-02 ] |
|
If ALTER MONITOR configuration changes are persisted in /var/lib/maxscale/maxscale.cnf.d/, then I think it would be kind of confusing if they did *not* take precedence over the options set in the main maxscale.cnf. Rather than changing the precedence, would it make sense to be able to set a global option that prevents ALTER MONITOR changes (and similar changes) from being saved to /var/lib/maxscale/maxscale.cnf.d/? |
| Comment by markus makela [ 2019-04-03 ] |
|
muhammad.irfan please correct me if I am wrong but I believe the solution to the problem at hand is the one GeoffMontee described: add a parameter that prevents persistence of runtime configuration changes. Having the main configuration take precedence over the runtime generated one is not reasonable as it is can break the combined configuration. |
| Comment by markus makela [ 2019-04-03 ] |
|
Added load_persisted_configs parameter that is enabled by default. If configured with load_persisted_configs=false, the files in /var/lib/maxscale/maxscale.cnf.d/ are ignored on startup. |