Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
21.06.16, 22.08.13, 23.02.10, 23.08.6, 24.02.2
-
None
-
MXS-SPRINT-216
Description
If readwritesplit is configured with max_slave_connections=0 and a switchover happens, reads will still use the old master server even if the new master would be available. When the next write occurs, the master is replaced and the stale connection is discarded. The expected behavior with max_slave_connections=0 is that as soon as the staleness of the master is detected, the connection should be discarded. If no replacement is available, the read should not proceed even if a connection to a server with the Slave status would be available.
Attachments
Issue Links
- relates to
-
MXS-5085 max_slave_connections=0 may create slave connections after a switchover
- Closed