[MXS-4244] Parameter to prevent promotion of a replica which has had Error 1236 Created: 2022-08-12  Updated: 2023-10-09  Resolved: 2022-11-21

Status: Closed
Project: MariaDB MaxScale
Component/s: failover, mariadbmon
Affects Version/s: None
Fix Version/s: 22.08.2

Type: New Feature Priority: Major
Reporter: Ben Grieser Assignee: Esa Korhonen
Resolution: Won't Fix Votes: 0
Labels: None

Sprint: MXS-SPRINT-170, MXS-SPRINT-171

 Description   

Requesting a way to prevent MariaDB Monitor from promoting a replica which has had an Error 1236 - ER_MASTER_FATAL_ERROR_READING_BINLOG - or similar fatal replication error.

Suggesting a parameter for MariaDB Monitor, something like auto_failover_strict_mode.

In the referenced support case, customer had a primary with two replicas. One replica was out of sync due to a 1236 error. In a subsequent failover situation, the out of sync replica was promoted to primary, causing the other nodes to be out of sync later.

A parameter such as auto_failover_strict_mode would have prevented MariaDB Monitor from promoting the out of sync replica, even if that would result in a longer outage.


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