[MXS-1503] Master reconnection Created: 2017-10-30  Updated: 2018-04-12  Resolved: 2018-04-03

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: None
Fix Version/s: 2.3.0

Type: New Feature Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 2
Labels: None

Issue Links:
Blocks
blocks MXS-1723 Delayed connection creation Closed
PartOf
includes MXS-1753 Create more master re-connection tests Closed
Epic Link: Transparent master failover
Sprint: MXS-SPRINT-54

 Description   

Overview

If readwritesplit loses the connection to the master, it is possible for the client session to go into read-only mode if the master_failure_mode is set to fail_on_write or error_on_write. If a master server becomes available when the session is in read-only mode, it should be possible to reconnect to the same master.

Task Details

  • Detect when new masters are available
  • Refactor connection creation code to treat master and slave servers the same way
Generated at Thu Feb 08 04:07:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.