[MXS-1504] Master migration Created: 2017-10-30  Updated: 2018-04-17  Resolved: 2018-04-17

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

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

Epic Link: Transparent master failover

 Description   

Overview

If the master server of the cluster changes mid-session, it should be possible for the slave servers to use this new server. For Galera clusters, node corruption due to master migration is not possible. Master-slave clusters are also free of node corruption if the master failover is performed in a way that blocks new writes for occurring on the old master e.g. with SET GLOBAL read_only=ON.

Task Details

A new master can be taken into use if and only if:

  • Autocommit is enabled
  • No transactions are open on the old master

Write queries with autocommit enabled that are already in progress when the switch happens do not prevent the master migration from taking place.


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