[MDEV-15875] the lost of "BEGIN" in mariadb server's binlog result in our lots of projects not working Created: 2018-04-16  Updated: 2022-04-19  Resolved: 2022-04-19

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

Type: Bug Priority: Major
Reporter: doathink Assignee: Sujatha Sivakumar (Inactive)
Resolution: Duplicate Votes: 0
Labels: binlog
Environment:

any*

Attachments: JPEG File 1523853121489.jpg     JPEG File 1523853247199.jpg     JPEG File WechatIMG228.jpeg     JPEG File WechatIMG230.jpeg    
Issue Links:
Duplicate
duplicates MDEV-7850 Extend GTID Binlog Events with Thread Id In Progress
duplicates MDEV-20925 Add thread id and Transaction length ... Closed
PartOf
is part of MDEV-20925 Add thread id and Transaction length ... Closed

 Description   

we have developed lots of projects based on mysql/mariadb Binlog, but in newest version of mariadb server, the BEGIN event have lost in row based binlog, which result in our projects not working at all. but in Oracle's mysql, the BEGIN event still been there.

what happened on Mariadb? is it a bug? this issue is very critical to our projects, if it can not included in, we have only one choice: choose to use Oracle/MySQL.

in attachments, WechatIMG230.jpeg is Mariadb, the BEGIN is included to GTID event, so there have lost the BEGIN event info, such as thread id..., detailed info as 1523853247199.jpg, WechatIMG228.jpeg is Oracle/MySQL, the BEGIN is still an alone event, I can read the thread id from it, detailed info as 1523853121489.jpg

 Comments   
Comment by doathink [ 2018-08-15 ]

how about this problem?

Comment by Sergei Golubchik [ 2018-08-15 ]

Unfortunately, this bug report has missed the 10.2.17 release, so now there may be no activity here until closer to the 10.2.18 release. See https://jira.mariadb.org/ for the planned release dates.

Comment by doathink [ 2018-08-16 ]

OK，I will continue to pay attention，thanks

Comment by Andrei Elkin [ 2018-11-06 ]

doathink, thanks for the report!

In MariaDB the transaction start event in binlog is Gtid_log_event, that carries out transaction identification
and its BEGIN Query_log_event. Indeed thread_id info is missed out in our Gtid_log_event printout and this
can be fixed quickly. I wonder if this action alone would be satisfactory for you? It is also possible to print Gtid_log_event out
in the mysql way, sort of masquerading them. But that's even less difficult to do with help of a small filter script piping in
mysqlbinlog output.

Could you please suggest your preference?

Regards,

Andrei Elkin

Comment by doathink [ 2018-12-18 ]

thanks for Andrei Elkin very much.
I only need the BEGIN event, which include the thread_id, it enough. it would be satisfactory for me very good.

thanks again.

Comment by Andrei Elkin [ 2019-07-17 ]

I new thread_id can be added to Gtid_log_event, and as it's the user visible change I think it may go only to the current development branch of 10.5.

Comment by Andrei Elkin [ 2020-09-03 ]

MDEV-20925 generalizes this case and there's been actual work on it, so this one can
be closed as a dup.

Comment by Sachin Setiya (Inactive) [ 2020-10-02 ]

MDEV-20925 is closed without fixing, So I am opening this issue

Generated at Thu Feb 08 08:24:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.