NAME

       filter_mysqlbinlog - Trimming ROLLBACK statements and equivalent BINLOG events added by mysqlbinlog. This
       script is now obsolete.

SYNOPSIS

       mysqlbinlog binary_or_relay_log_file | filter_mysqlbinlog

       Note that this script is now obsolete and not used by MHA by default.

DESCRIPTION

       mysqlbinlog command provided by Oracle implicitly adds ROLLBACK statements and equivalent BINLOG events.
       But this causes problems when recovering slave servers. To recover slaves, MHA might need to apply the
       following binlog events.
        1) Relay log events from Relay_Log_Pos to the end of the relay log file
        2) Differential relay log events from the latest slave
        3) Differential binary log events from the dead master mysqlbinlog command needs to be executed on these
       files separately. If a transaction does not end by 1) or 2), implicit ROLLBACK event rolls back the
       transaction, which will result in inconsistency.  filter_mysqlbinlog is a tool to fix this issue.  Note
       that ROLLBACK statements themselves are added in usual situations. For example, when you execute 1.
       BEGIN; 2. Updating transactional tables 3. Updating non-transactional tables  4. ROLLBACK, a ROLLBACK
       statement is written to the binary log to rollback transactional queries. This is normal situation so
       filter_mysqlbinlog must not remove all ROLLBACK events.

       Note that this script is now obsolete and not used by MHA by default.