Upgrading MariaDB MaxScale from 2.4 to 2.5
Upgrading MariaDB MaxScale from 2.4 to 2.5
This document describes possible issues when upgrading MariaDB MaxScale from version 2.4 to 2.5.
For more information about MaxScale 2.5, refer to the ChangeLog.
Before starting the upgrade, any existing configuration files should be backed up.
Authentication
The credentials used by services now require additional grants. For a full list of required grants, refer to the protocol documentation.
MariaDB-Monitor
The settings detect_stale_master
, detect_standalone_master
and
detect_stale_slave
are replaced by master_conditions
and
slave_conditions
. The old settings may still be used, but will be removed in
a later version.
Password encryption
The encrypted passwords feature has been updated to be more secure. Users are
recommended to generate a new encryption key and and re-encrypt their passwords
using the maxkeys
and maxpasswd
utilities. Old passwords still work.
Columnstore Monitor
It is now mandatory to specify in the configuration what version the monitored Columnstore cluster is.
[CSMonitor] type=monitor module=csmon version=1.5 ...
Please see the documentation for details.
New binlog router
The binlog router delivered with MaxScale 2.5 is completely new and not 100% backward compatible with the binlog router delivered with earlier MaxScale versions. If you use the binlog router, carefully assess whether the functionality provided by the new one fulfills your requirements, before upgrading MaxScale.
MaxAdmin has been removed
Remove all config section related to Maxadmin from the config file, like services with router=cli and listener with protocol=maxscaled.