Sign up ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am testing MySQL Cluster 7.2. I have two servers, mysql1 and mysql2. I want the management server and two data nodes to run on mysql1 and two other data nodes to run on mysql2. My config.ini file looks like this:


[ndbd default]






With this configuration I would expect, as per the MySQL Cluster documentation, that the two data nodes 3 and 4 would be in nodegroup 0, while the two data nodes 13 and 14 would be in nodegroup 1.

However, when I start everything up and show the nodes, I see this:

Connected to Management Server at: localhost:1186
Cluster Configuration
[ndbd(NDB)]     4 node(s)
id=3    @  (mysql-5.5.30 ndb-7.2.12, starting, Nodegroup: 0, Master)
id=4    @  (mysql-5.5.30 ndb-7.2.12, starting, Nodegroup: 0)
id=13   @  (mysql-5.5.30 ndb-7.2.12, starting, Nodegroup: 0)
id=14   @  (mysql-5.5.30 ndb-7.2.12, starting, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @  (mysql-5.5.30 ndb-7.2.12)

[mysqld(API)]   1 node(s)
id=50 (not connected, accepting connect from any host)

Everything seems to be in nodegroup 0! What do I have to do to get 3 and 4 in one group and 13 and 14 in another?

share|improve this question
I'm having the same question. I asked it here.… And I started a bounty on your question as it seems a common problem. – Bhathiya Dec 29 '13 at 20:28

1 Answer 1

This seems to be a bug [1] in MySQL. It happens because your data nodes are still starting. Node-group IDs should be shown correctly once they are started completely.


share|improve this answer
That bug is 7 years old, I'd be surprised if it wasn't already fixed. – shearn89 Mar 24 at 10:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.