[MXS-3074] one master , one binlog-server , three slave , how to detect_replication_lag Created: 2020-07-16  Updated: 2020-11-24  Resolved: 2020-11-24

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Bug Priority: Major
Reporter: wilsonlau Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None


 Description   

how to detect_replication_lag under binlog-server replication mode

 Comments   
Comment by markus makela [ 2020-07-20 ]

If you use mariadbmon, I think it will detect replication lag correctly as it uses the Seconds_Behind_Master as the value. Do you have an example case where this does not work?

Comment by wilsonlau [ 2020-07-28 ]

configs:
----------------
[node1]
type=server
address=galera-0.galera-headless.galera
port=3306
protocol=MariaDBBackend

[binlogserver]
type=server
address=binlogx-headless.maxscale
port=3306
protocol=MariaDBBackend
rank=secondary

[slave1]
type=server
address=mariadb-0.mariadb-headless.mariadb-x
port=3306
protocol=MariaDBBackend

[slave2]
type=server
address=mariadb-1.mariadb-headless.mariadb-x
port=3306
protocol=MariaDBBackend

---------------
[galera]
type=monitor
module=galeramon
servers=node1
user=xxxx
password=xxx

[slave]
type=monitor
module=mariadbmon
servers=slave1,slave2,binlogserver
user=xxxx
password=xxx

Comment by wilsonlau [ 2020-07-28 ]

warning: [mariadbmon] Error during monitor permissions test for server 'binlogserver': Query 'SHOW SLAVE STATUS;' failed: 'In line 1:
Error! Expecting `end of input`:
SHOW SLAVE STATUS;
________________^
'.

Comment by markus makela [ 2020-10-19 ]

What version did you test this with? Can you try and see if the latest 2.5 release works?

Comment by markus makela [ 2020-11-24 ]

Closing as Fixed in 2.5.5 until we know whether the fixes in it solve this problem.

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