MySQL Bugs: #59825: Data loss after crash at half_binlogged

Bug #59825	Data loss after crash at half_binlogged_transaction for binlog crash-safe
Submitted:	30 Jan 2011 20:33	Modified:	1 Feb 2011 9:34
Reporter:	Serge Kozlov	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	mysql-trunk-wl5493	OS:	Any
Assigned to:	Daogang Qu	CPU Architecture:	Any
Tags:	crash, half_binlogged_transaction, myisam, nuts, replication

Description:
The bug is similar bug#59622 except the storage engine and crash point. After crash at half_binlogged_transaction for a non-transactional table (MyISAM) the integrity is lost. 

Notes:
1. It is not 100%-reproducible because the statements is generated dynamically by test case. But at least half of runs will fail
2. Loss integrity means that recent statements before crash were applied on master but didn't appear on slave.

How to repeat:
<NUTS_HOME>./bin/nuts.pl --build=<PATH_TO_BUILD> --suite=rep_func --test=crash_safe_master --verbose --combination=myisam

This is an expected behaviour if a non-transactional engine such as MyIsam is used. For non-transactional engines you just need to check if the master can continue normal operations after a crash and a possible corrupted binary log.