Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.5
-
MXS-SPRINT-170
Description
We have master_reconnect setting since 2.3.x, but current documentation:
https://mariadb.com/kb/en/mariadb-maxscale-25-readwritesplit/#master_reconnection
does not include any example on how the connection will work (what client side will get) when it's enabled. There are many preconditions listed, and one may assume (without reading that KB page) that connection to current master will be transparently re-routed to a new master, while this may not be true and the feature is more about changing read only status for the connections to promoted slave (correct me if I am wrong).
Please, elaborate and show some use cases for this feature with examples (in KB and/or Enterprise Documentation).