Hi,
This is correct behaviour, status on a node is only applicable to data nodes.
Also start and stop of nodes can only be done on data nodes and management
server nodes.
Rgrds Mikael
Arnd Kohlen wrote:
> Hello
>
> I installed mysql 5.0.7-beta3 cluster and it seems
> all running fine... it seems...
>
> Here is the output of ndb_mgm "show":
> ndb_mgm> show
> Cluster Configuration
> ---------------------
> 2 node(s)
> id=2 @192.168.200.176 (Version: 5.0.7,
> Nodegroup: 0, Master)
> id=3 @192.168.200.177 (Version: 5.0.7,
> Nodegroup: 0)
>
> 1 node(s)
> id=1 @192.168.200.175 (Version: 5.0.7)
>
> 2 node(s)
> id=4 @192.168.200.179 (Version: 5.0.7)
> id=5 @192.168.200.178 (Version: 5.0.7)
>
> There are two data nodes (.176 + .177) and two sql
> nodes (.178 + .179).
>
> Everything seems fine but when trying to get the
> status of those nodes I receive the following
> error:
>
> ndb_mgm> 2 status
> Node 2: started (Version 5.0.7)
>
> ndb_mgm> 4 status
> Node 4: not connected
>
> ndb_mgm> 5 status
> Node 5: not connected
>
> The configuration file on the management node is:
> --------------------------------------------------
> --------
>
>
> NoOfReplicas=2
> DataMemory=80M
> IndexMemory=52M
>
>
> portnumber=2202
>
>
> hostname=192.168.200.175
> datadir=/var/lib/mysql-cluster
>
>
> hostname=192.168.200.176
> datadir=/home/data/mysql/3306
>
>
> hostname=192.168.200.177
> datadir=/home/data/mysql/3306
>
>
>
>
> The configuration on the sql-nodes (/etc/my.cnf):
> --------------------------------------------------
> ------
>
> ndbcluster
> ndb-connectstring=192.168.200.175
> datadir = /home/data/mysql/3306
>
>
> ndb-connectstring=192.168.200.175
>
> Its not just the status message resulting in an
> error. Any start or stop operation doesn't have an
> affect on the sql nodes.
>
> What's wrong?
Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:
http://mikaelronstrom.blogspot.com