Bug #69818 Replication IP is broken but slave IO thread is YES
Submitted: 23 Jul 2013 1:28 Modified: 21 Jul 2014 17:46
Reporter: Seonghwan Kim Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version: OS:Linux
Assigned to: CPU Architecture:Any
Tags: io, replication

[23 Jul 2013 1:28] Seonghwan Kim
Description:
Hi,
I'm Mysql DBA. I have a One problem.

I'm organize MySql Replication (Master <-- Slave).
with duplication network.
Linux server IP : 172.xxx.xxx.xxx (public network)
mysql replicaiton IP : 10.xxx.xxx.xxx (heart beat network)

when replication Ip is broken, but.. Slave_IO_Running: YES ..
and Approximately 10~15 minutes after. IO thread is change.. YES => connecting..

Replication IP check is So Late.
Is this bug?? or normal??

If.. It's a NORMAL, I have questions.
(1)How can I reduce the replication IP check time. 
   (10~15Minute => 1Min, or more short, or Immediately)
   How can I change the related configurateions.

(2)How can I change the comment, Slave_IO_Running : connecting => NO
   I want message change.(connecting => NO)

Please Help Me..

From. Seonghwan Kim
auidy@naver.com

How to repeat:
MySql is NOT check Replication IP immediately.

Suggested fix:
MySql is check Replication IP immediately.
[21 Jul 2014 17:46] Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Please adjust options slave-net-timeout (http://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_slave-...) and master-retry-count (http://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master...)