Bug #54741 MySQL Cluster 7.0
Submitted: 23 Jun 2010 14:32 Modified: 25 Jun 2010 14:58
Reporter: Anirudh Tamsekar Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S5 (Performance)
Version:7.0 OS:Linux
Assigned to: CPU Architecture:Any
Tags: Cannot Connect to Management node

[23 Jun 2010 14:32] Anirudh Tamsekar 
Description:
[root@win4 mysql-cluster]# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2 (not connected, accepting connect from 10.5.20.35)
id=3 (not connected, accepting connect from 10.5.20.46)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @10.5.20.31  (mysql-5.1.41 ndb-7.0.13)

[mysqld(API)]   2 node(s)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)

ndb_mgm> Node 2: Forced node shutdown completed. Occured during startphase 0. Initiated by signal 11. Caused by error 6000: 'Error OS signal received(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.
Node 3: Forced node shutdown completed. Occured during startphase 0. Initiated by signal 11. Caused by error 6000: 'Error OS signal received(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.

ndb_mgm> show
Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2 (not connected, accepting connect from 10.5.20.35)
id=3 (not connected, accepting connect from 10.5.20.46)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @10.5.20.31  (mysql-5.1.41 ndb-7.0.13)

[mysqld(API)]   2 node(s)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)

ndb_mgm> 2 RESTART
Restart failed.
*  2003: Restart failed
*        5000-No contact with the process (dead ?).: Permanent error: Application error

ndb_mgm> 3 RESTART
Restart failed.
*  2003: Restart failed
*        5000-No contact with the process (dead ?).: Permanent error: Application error

ndb_mgm>

How to repeat:
This happened right after I restarted the Management server using ndb_mgmd.

P.S: Reporting bug for the first time, kindly revert if any further details are required.

Suggested fix:
[24 Jun 2010 9:03] Anirudh Tamsekar 
This error was due to the DataMemory and IndexMemory variables defined under the [NDBD DEFAULT]
DataMemory= 3G
IndexMemory= 2G

Once I commented out those variables, management server was fine.
The values I mentioned did not consider the RAM I have in my server. It is best to use the appropriate values based on the H/W configuration.