MySQL Bugs: #19454: Some values of MaxNoOfTriggers can stop a server

Bug #19454	Some values of MaxNoOfTriggers can stop a server
Submitted:	1 May 2006 8:16	Modified:	22 Dec 2006 3:42
Reporter:	Serge Kozlov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	4.1 ->	OS:	Linux (Linux FC4)
Assigned to:	justin he	CPU Architecture:	Any

Description:
For some values MaxNoOfTriggers   (probably it's true for others attributes) the server (where ndbd nodes are starting) can be inaccessible after start of ndbd nodes.

Attempt to connect to managment server (it started on same server too) returns following error:

Warning, event thread startup failed, degraded printouts as result, errno=0
Connected to Management Server at: ndb16:1186

Could not get status
*     0: No error
*        Executing: ndb_mgm_disconnect
ndb_mgm>
ndb_mgm>

How to repeat:
1. Create simple config.ini: 1 ndb_mgmd, 1 mysqld, 2 ndbd, 2 replicas. All nodes will start on same server.
2. Add MaxNoOfTriggers = 2M to configuration.
3. Start a cluster.
4. If cluster start successfully then try increase MaxNoOfTriggers.
5. If cluster isn't started with 'Job Buffer Full' error then try decrease MaxNoOfTriggers.

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:

  http://lists.mysql.com/commits/11603

ChangeSet@1.2255, 2006-09-08 16:41:30+08:00, Justin.He@qa3-104.qa.cn.tlan +12 -0
  BUG#19454, Some values of MaxNoOfTriggers can stop a server
  
  the main modifications is following:
  1. move the default parameter definition from ConfigInfo.cpp to a new header file
  2. correct the segmentation fault when malloc mem in setSize() in ArrayPool.hpp
  3. add a new mgmapi for map the parameter ID to it's corresponding name
  4. modifiy something because the change of class 'ConfigInfo'

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:

  http://lists.mysql.com/commits/11604

ChangeSet@1.2255, 2006-09-08 16:46:05+08:00, Justin.He@qa3-104.qa.cn.tlan +12 -0
  BUG#19454, Some values of MaxNoOfTriggers can stop a server
  
  the main modifications is following:
  1. move the default parameter definition from ConfigInfo.cpp to a new header file
  2. correct the segmentation fault when malloc mem in setSize() in ArrayPool.hpp
  3. add a new mgmapi for map the parameter ID to it's corresponding name
  4. modifiy something because the change of class 'ConfigInfo'

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:

  http://lists.mysql.com/commits/12698

ChangeSet@1.2297, 2006-09-28 18:55:20+08:00, Justin.He@qa3-104.qa.cn.tlan +13 -0
  Bug #19454, Some values of MaxNoOfTriggers can stop a server
  1. move the default parameters definition from ConfigInfo.cpp to a new
  file
  2. correct the segmentation fault in ArrayPool.hpp:setSize()
  3. add a new mgmapi function to get info of a parameter
  4. modify something because the changes of class ConfigInfo

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:

  http://lists.mysql.com/commits/12811

ChangeSet@1.2297, 2006-09-29 14:51:21+08:00, Justin.He@qa3-104.qa.cn.tlan +13 -0
  Bug #19454, Some values of MaxNoOfTriggers can stop a server
  1. move the default parameters definition from ConfigInfo.cpp to a new file
  2. correct the segmentation fault in ArrayPool.hpp:setSize()
  3. add a new mgmapi function to get info of a parameter
  4. modify something because the changes of class ConfigInfo

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/

Documented bugfix in 5.1.14 changelog.