Bug #28899 not possible to set separate watchdog timeout at startup
Submitted: 5 Jun 2007 14:55 Modified: 11 Jun 2007 21:08
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Tomas Ulin CPU Architecture:Any

[5 Jun 2007 14:55] Tomas Ulin
for large systems malloc() system call can take a long time, this will cause ndbd to go down on watchdog timeout.  Setting watch dog timeout higher to avaod this makes the timeout to large to make any use when system is up and running

this is especially true when using lock pages in main memory

How to repeat:

Suggested fix:
have separate watchdog timeout for memory allocation start phase
[5 Jun 2007 15:09] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[11 Jun 2007 11:39] Bugs System
Pushed into 5.1.20-beta
[11 Jun 2007 21:08] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at


Documented new cluster configuration parameter in 5.1.20 changelog and Defining Data Nodes section of Cluster chapter in 5.1 Manual.
[3 Jul 2007 6:47] Jon Stephens
Also documented for telco-6.2.3 release.