Bug #82359 mysql skipped binary log position and starts from skipped postion
Submitted: 27 Jul 2016 13:11 Modified: 9 Aug 2016 9:35
Reporter: susanto mahato Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.6 OS:Ubuntu
Assigned to: CPU Architecture:Any
Tags: mysql skipped binary log position and starts from skipped postion

[27 Jul 2016 13:11] susanto mahato
Description:
We faced some EBS issue on one of the multi level replication slave.Due to this mysql went for defunct mode.

when EBS got recovered , we observed it skipped 16 min binary logs.

And it  continue with skipped binary log position.

it skipped around  16 min data.

As per the replication topology it should start when slave stopped.But it skipped and continue with skipped binary log position .

can you please confirm why it behave like this?

How to repeat:
1. create muti level replication setup 1-> 2- > 3,
 2.create some EBS issue on mysql datadir on slave 2 .
3. Mysql will went for defunct mode.
4. check the mysql binary position.
[9 Aug 2016 9:35] Umesh Shastry
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

Which MySQL version are you using? Are you using GTID? Please provide exact repeatable test case, conf file used. See, related Bug #69943

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.