Bug #37847 Bug #28618 was not fixed in version 5.0
Submitted: 3 Jul 2008 20:26 Modified: 11 Dec 2008 22:21
Reporter: Sveta Smirnova
Status: Won't fix
Category:Server: Replication Severity:S2 (Serious)
Version:5.0 bzr OS:Any
Assigned to: Target Version:
Triage: Triaged: D2 (Serious) / R4 (High) / E4 (High)

[3 Jul 2008 20:26] Sveta Smirnova 
Description:
Bug #28618 (Skipping into the middle of a group with SQL_SLAVE_SKIP_COUNTER is possible)
was not fixed in version 5.0.

How to repeat:
See Bug #28618
[16 Jul 2008 19:26] Michael Widenius 
This should be trivial to fix in 5.0 (as 5.0 code in this regard is much simpler than
5.1).

Suggested fix:
- Ensure we don't get a rotate event between two associated events in  
MYSQL_BIN_LOG::write() for two related events.
[29 Aug 2008 8:14] Lars Thalmann 
Regarding Monty's comment:

The rotate is not the problem, the problem is that the group log 
position is updated before the entire group has finished executing, 
causing it to start executing from the middle of a group if
the slave crashes for some reason.
[11 Dec 2008 22:22] Omer BarNir 
Issue will not be fixed in 5.0 based on risk and effort associated