[MXS-1142] maxbinlogcheck to remove transaction from binlog Created: 2017-02-15  Updated: 2018-03-20  Resolved: 2017-02-17

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

Type: New Feature Priority: Minor
Reporter: Michaël de groot Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MXS-1141 maxbinlogcheck to replace an event wi... Closed
Relates
relates to MXS-1728 Please document ignorable events in M... Closed
Sprint: 2017-28

 Description   

Hi,

After being able to nullify one event from the binary log, I think it would be great if the maxbinlogcheck utitlity could remove/nullify/make ignorable a whole transaction from the binlog.

So, for example: maxbinlogcheck --remove-transaction=pos
Could look in the binlog to find the previous BEGIN statement and then look further until it finds the next COMMIT. Then, when the positions are known, make everything in between ignorable.

Thank you!

 Comments   
Comment by Massimiliano Pinto (Inactive) [ 2017-02-16 ]

options: -f -T 6311

2017-02-16 17:19:35 notice : [binlogrouter] >>> Position 6311 belongs to a transaction started at pos 6224.

2017-02-16 17:19:35 notice : [binlogrouter] === Replacing all events of Transaction at pos 6224 with IGNORABLE EVENT event type
2017-02-16 17:19:35 notice : [binlogrouter] Replace event (GTID Event) at pos 6224 with an IGNORABLE EVENT 2017-02-16 17:19:36 notice : [binlogrouter] Replace event (Table Map Event) at pos 6266 with an IGNORABLE EVENT
2017-02-16 17:19:36 notice : [binlogrouter] Replace event (Write Rows Event (v1)) at pos 6311 with an IGNORABLE EVENT 2017-02-16 17:19:36 notice : [binlogrouter] Replace event (Query Event) at pos 6349 with an IGNORABLE EVENT

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