[#MXS-1598] heartbeat replication don't support multimaster

[MXS-1598] heartbeat replication don't support multimaster Created: 2018-01-09 Updated: 2020-08-25 Resolved: 2018-11-16
Status:	Closed
Project:	MariaDB MaxScale
Component/s:	mariadbmon
Affects Version/s:	None
Fix Version/s:	2.3.2

Type:

New Feature

Priority:

Major

Reporter:

Richard Stracke

Assignee:

Esa Korhonen

Resolution:

Fixed

Votes:

Labels:

None

Sprint:

MXS-SPRINT-67, MXS-SPRINT-68, MXS-SPRINT-69, MXS-SPRINT-70

Description

Maxscale configured with

Service

router=readwritesplit

master_accept_reads=true

max_slave_replication_lag

Monitor

module=mysqlmon

multimaster=true

detect_replication_lag=true

Setup
Master1 - Master 2 - Salve

2018-01-08 14:42:40   notice : Server changed state: db-node1[x.x.x.x1:3306]: new_master. [Running] -> [Master, Running]

2018-01-08 14:42:40   notice : Server changed state: db-node2[x.x.x.2:3306]: new_master. [Running] -> [Master, Running]

2018-01-08 14:42:40   notice : Server changed state: db-node3[X.X.X.3:3306]: new_slave. [Running] -> [Slave, Running]

Heartbeat tables will only be filled on Master1 (x.x.x.1) and Slave (x.x.x.3)

possible root cause:

heartbeat did not recognize master as a slave

 if ((!SERVER_IN_MAINT(ptr->server)) && SERVER_IS_RUNNING(ptr->server))

                    if (ptr->server->node_id != root_master->server->node_id &&

                        (SERVER_IS_SLAVE(ptr->server) ||

                         SERVER_IS_RELAY_SERVER(ptr->server)))

Comments

Comment by Dipti Joshi (Inactive) [ 2018-09-19 ]

Have we tested it esa.korhonen?

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