Bug #78897 documentation correction for --connect-retries and --connect-retry-delay

Submitted: 21 Oct 2015 11:26 Modified: 27 Oct 2015 8:03
Reporter: Sanjana Dulipeta Sridhar Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Documentation Severity:S2 (Serious)
Version:7.4 OS:Any
Assigned to: Jon Stephens CPU Architecture:Any

[21 Oct 2015 11:26] Sanjana Dulipeta Sridhar
Description:
The documentation descriptions for --connect-retries and --connect-retry-delay are not entirely correct.

They need to be fixed in the links below:

1) https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-program-options-common.html
description change required: "attempt" to "reattempt"
--connect-retries=0 does not mean no attempts at all. There are no 'reattempts', i.e a single attempt is always made;
--connect-retry-delay=0 does not mean wait forever. It means there is no delay between the retries.

2) https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-program-options-common.html#option_n... 
(description change & spelling error: "befpore" needs to be changed to "before")

3) https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-program-options-common.html#option_n... 
(description change & spelling error: "befpore" needs to be changed to "before")

How to repeat:
ndb_config --connect-string=no_such_host --connect-retry-delay=0
ndb_config --connect-string=no_such_host --connect-retries=0

Suggested fix:
--connect-retries : Set the number of times to reattempt a connection before giving up. 0 means a single attempt.
--connect-retry-delay :Set the number of seconds to wait per attempt to make a connection before giving up. 0 means no delay between retries.
[27 Oct 2015 8:03] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.