Bug #109534 Suggest to pass the current timestamp in XID_EVENT event
Submitted: 4 Jan 2023 10:54 Modified: 4 Jan 2023 12:33
Reporter: Fangxin Flou (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:all, 8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: replication, Seconds Behind Master

[4 Jan 2023 10:54] Fangxin Flou
We can often see Seconds_Behind_Master value jumping for long or big transactions. It's very clearly that the current logic is not good enough to generate correct value.

How to repeat:

Suggested fix:
Suggest to pass the current timestamp (with extra 8 bytes space) in XID_EVENT (row based replication) and QUERY_EVENT (statement event), then we can maintain a correct last_master_timestamp value to generate a more correct  Seconds_Behind_Master value.
[4 Jan 2023 12:33] MySQL Verification Team
Hello Fangxin Flou,

Thank you for the suggestion and feature request!