Bug #33237 NDB_MGM 'eat' 99% cpu utilization
Submitted: 14 Dec 2007 10:01 Modified: 20 Feb 2008 21:54
Reporter: justin he Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:Linux
Assigned to: CPU Architecture:Any

[14 Dec 2007 10:01] justin he 
Description:
mysql-5.1-telco-6.3,

after an abnormal kill all data nodes and mysql server nodes,
ndb_mgm use 99% cpu, but do some operation on ndb_mgm, seems it's okay then.

How to repeat:
run a cluster and ndb_mgm tool, kill all ndbd and mysqld (do not shutdown normally),
then will find ndb_mgm use 99% cpu ...
[14 Dec 2007 12:43] 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:

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

ChangeSet@1.2579, 2007-12-14 13:43:48+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #33237 NDB_MGM 'eat' 99% cpu utilization
[7 Jan 2008 15:27] Jon Stephens 
Documented bugfix in 5.1.23-ndb-6.3.7 changelog as follows:

        When all data and SQL nodes in the cluster were shut down
        abnormally (that is, other than by using STOP
        in the cluster management client), ndb_mgm
        used excessive amounts of CPU.

Left status as PP pending further merges.
[7 Jan 2008 16:03] Jon Stephens 
Also documented fix in 5.1.23-ndb-6.2.10 changelog. Left bug status unchanged.
[20 Feb 2008 16:02] Bugs System 
Pushed into 5.0.58
[20 Feb 2008 16:03] Bugs System 
Pushed into 5.1.24-rc
[20 Feb 2008 16:04] Bugs System 
Pushed into 6.0.5-alpha
[20 Feb 2008 21:54] Jon Stephens 
Also documented for 5.0.58, 5.1.24, and 6.0.5.