| Bug #22257 | The default value of StartFailureTimeout of NDB data node is not 60000 | ||
|---|---|---|---|
| Submitted: | 12 Sep 2006 2:54 | Modified: | 14 Sep 2006 9:30 |
| Reporter: | david li | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 4.1 -> | OS: | |
| Assigned to: | Jon Stephens | CPU Architecture: | Any |
[12 Sep 2006 6:54]
Valeriy Kravchuk
Thank you for a problem report. Verified just as described with current 5.0.26-BK sources. It is either a bug or a documentation request to change http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-ndbd-definition.html as suggested here.
[14 Sep 2006 9:30]
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, and will be included in the next release of the relevant products. Updated docs per submitter info.
Description: In the reference manual, 15.4.4.5. Defining Data Nodes. StartFailureTimeout The default value is 60000 milliseconds (60 seconds). But in source code, the default value of StartFailureTimeout is 0 (infinite). ndb/src/mgmsrv/ConfigInfo.cpp const ConfigInfo::ParamInfo ConfigInfo::m_ParamInfo[] = { ... { CFG_DB_START_FAILURE_TIMEOUT, "StartFailureTimeout", DB_TOKEN, "Time to wait before terminating. 0=Wait forever", ConfigInfo::CI_USED, true, ConfigInfo::CI_INT, "0", ----> the default value "0", STR_VALUE(MAX_INT_RNIL) }, ... How to repeat: as above. Suggested fix: The default value of StartFailureTimeout should be 0 (infinite).