[MXS-1141] maxbinlogcheck to replace an event with ignorable event 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: Major
Reporter: Michaël de groot Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MXS-1142 maxbinlogcheck to remove transaction ... Closed
Relates
relates to MXS-1728 Please document ignorable events in M... Closed
Sprint: 2017-28

 Description   

Hi,

MaxScale binlog server is a great tool for point in time recovery. We use maxscale to continuously copy the binlogs to another machine.
Let's say a disaster occurs, somebody executes DROP TABLE databse.table;

We could do point in time recovery by restoring a backup and making the backup slave to MaxScale. It would replicate and replicate the disaster as well.

It would be great if we can nullify the event (make it ignorable by the replication slave). This way, we can remove the DROP TABLE from the binlog file and replicate all other events from MaxScale.

For example --remove-event=start_pos to remove the even from start_pos until the end of the event.

Thank you!



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

Current code for -R $pos is in develop branch

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