[MXS-1741] Can't change maxscale_id for replication_heartbeat Created: 2018-03-26  Updated: 2018-08-29  Resolved: 2018-08-29

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation, Monitor
Affects Version/s: 2.1.15
Fix Version/s: 2.3.0

Type: Bug Priority: Major
Reporter: Igor V. Lovalev Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

centos 6, maxscale 2.1.15, Percona Server 5.6.35-81.0



 Description   

Hi there! I have four maxscale instances running on different nodes with same mysql master-slave cluster. And i didn't find how to set maxscale_id for replication_heartbeat. maxscale_id always is zero.
(c) https://mariadb.com/kb/en/mariadb-enterprise/how-set-a-maxscale_id-for-replication_heartbeat/



 Comments   
Comment by Esa Korhonen [ 2018-08-29 ]

Because of changes to replication lag detection in 2.3, the entire Id setting has been removed.

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