[MDEV-31649] seconds behind master in slave status refers to its master's master if GTID enabled Created: 2023-07-08  Updated: 2023-07-08  Resolved: 2023-07-08

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.6.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Rick Pizzi Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

In a classic replication setup A -> B -> C , when I run "show slave status" on C, I expect Seconds_Behind_Master to report the delay in replication in respect to its master B.

If GTID are enabled however, it reports delay in respect to A, when in reality C is caught up with B - in fact, disabling GTIDs makes SBM correctly report zero.

I noticed that Gtid_IO_Pos has the GTID from A listed before the one from B. Could be the source of the issue, although I think that slave should search for B's GTID specifically and not just use the first in the list.

The two GTIDs have different domain ID, one more reason for C to ignore the one from A; unfortunately, it doesn't.



 Comments   
Comment by Rick Pizzi [ 2023-07-08 ]

never mind, diff. issue

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