Andrei 98ca71ab28 MDEV-28461 semisync-slave server recovery fails to rollback prepared transaction ...

that is not in binlog.

Post-crash recovery of --rpl-semi-sync-slave-enabled server
failed to recognize a transaction in-doubt that needed rolled back.
A prepared-but-not-in-binlog transaction gets committed instead
to possibly create inconsistency with a master (e.g the way it was observed
in the bug report).

The semisync recovery is corrected now with initializing binlog coordinates
of any transaction in-doubt to the maximum offset which is
unreachable.
In effect when a prepared transaction that is not found in binlog
it will be decided to rollback because it's guaranteed to reside
in a truncated tail area of binlog.

Mtr tests are reinforced to cover the described scenario.

2022-05-18 09:48:57 +02:00

..

include

Merge branch '10.5' into 10.6

2022-02-03 17:01:31 +01:00

r

MDEV-28461 semisync-slave server recovery fails to rollback prepared transaction

2022-05-18 09:48:57 +02:00

std_data

…

t

MDEV-28461 semisync-slave server recovery fails to rollback prepared transaction

2022-05-18 09:48:57 +02:00

combinations

…

disabled.def

MDEV-22008 rpl.rpl_semi_sync fails in bb, MDEV-24418 reenable binlog_truncate_innodb and binlog_spurious_ddl_errors, rpl_parallel_retry fails in bb

2020-12-18 19:31:51 +01:00