Bug #21491 --master-connect-retry should talk about --slave-net-timeout
Submitted: 7 Aug 2006 20:31 Modified: 16 Aug 2006 12:50
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: MC Brown CPU Architecture:Any

[7 Aug 2006 20:31] Jonathan Miller 
Description:
http://dev.mysql.com/doc/refman/5.1/en/replication-options.html

--master-connect-retry=seconds

The number of seconds that the slave thread sleeps before trying to reconnect to the master in case the master goes down or the connection is lost. The value in the master.info file takes precedence if it can be read. If not set, the default is 60. 

The above setting says nothing about the below setting, yet the below setting it what triggers the --master-connect-retry.

--slave-net-timeout=seconds

The number of seconds to wait for more data from the master before the slave considers the connection broken, aborts the read, and tries to reconnect. The first retry occurs immediately after the timeout. The interval between retries is controlled by the --master-connect-retry option. 

How to repeat:
N/A

Suggested fix:
--master-connect-retry=seconds

The number of seconds that the slave thread sleeps before trying to reconnect to the master in case the master goes down or the connection is lost. The value in the master.info file takes precedence if it can be read. If not set, the default is 60. NOTE: These retries are not invoked until the slave reaches the --slave-net-timeout
[8 Aug 2006 11:51] Jonathan Miller 
In addition, I believe a stop slave and start slave (i.e. cycling the slave) is need for these to take if the slave is all ready running.
/jeb
[16 Aug 2006 12:50] MC Brown 
I have updated the documentation with the relationship.