[MXS-3941] create_one_connection_for_sescmd() doesn't correctly replace m_current_master Created: 2022-01-08  Updated: 2022-07-07  Resolved: 2022-01-13

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 6
Fix Version/s: 6.2.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

If there are multiple servers labeled as master and the current master is down, a second connection to a different server that's a master is opened. The m_current_master variable isn't updated to reflect the new situation.

This is only a problem when the fix to MXS-3934 is in use. There it can cause a failing session command to be rapidly executed as the "new" master server is classified as a slave server. This in turn causes a failure to retry a session command.


Generated at Thu Feb 08 04:25:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.