Re: Multi MGMD node woes - Kris Buytaert - com.mysql.lists.cluster

6 messages in com.mysql.lists.clusterRe: Multi MGMD node woes

From	Sent On	Attachments
Joseph Miller	14 Apr 2005 17:06
Martin Skold	15 Apr 2005 00:48
Kris Buytaert	17 Jul 2006 03:47
Kris Buytaert	17 Jul 2006 04:18
Mikael Ronström	17 Jul 2006 05:15
Kris Buytaert	17 Jul 2006 06:14

Subject:	Re: Multi MGMD node woes
From:	Kris Buytaert (ml...@x-tend.be)
Date:	07/17/2006 04:18:53 AM
List:	com.mysql.lists.cluster

On Mon, 2006-07-17 at 12:47 +0200, Kris Buytaert wrote:

I've set this up before but I`m getting stuck with the 5.11beta version.

Getting back 2 my own setup.. It seems like I was a bit impatient to see the nodes started.

I can now see both nodes on my setup , altough it looks like this only happens after I started an ndbd node.

But the I can't connect to the local management console on the second node without a -c parameter.

I guess I`ll log that as a bug.

greetings

Kris

ndb_mgm -- NDB Cluster -- Management Client -- ndb_mgm> show Connected to Management Server at: 172.16.32.1:1186 Cluster Configuration

--------------------- [ndbd(NDB)] 2 node(s) id=3 @172.16.32.7 (Version: 5.1.11, Nodegroup: 0, Master) id=4 (not connected, accepting connect from 172.16.32.107)

[ndb_mgmd(MGM)] 2 node(s) id=1 @172.16.32.1 (Version: 5.1.11) id=2 @172.16.32.101 (Version: 5.1.11)

[mysqld(API)] 3 node(s) id=5 @172.16.32.7 (Version: 5.1.11) id=6 (not connected, accepting connect from any host) id=7 (not connected, accepting connect from any host)

ndb_mgm> -bash-3.00# ndb_mgm -c 172.16.32.101:1186 -- NDB Cluster -- Management Client -- ndb_mgm> show Connected to Management Server at: 172.16.32.101:1186 Cluster Configuration

--------------------- [ndbd(NDB)] 2 node(s) id=3 @172.16.32.7 (Version: 5.1.11, Nodegroup: 0, Master) id=4 (not connected, accepting connect from 172.16.32.107)

[ndb_mgmd(MGM)] 2 node(s) id=1 @172.16.32.1 (Version: 5.1.11) id=2 @172.16.32.101 (Version: 5.1.11)

[mysqld(API)] 3 node(s) id=5 @172.16.32.7 (Version: 5.1.11) id=6 (not connected, accepting connect from any host) id=7 (not connected, accepting connect from any host)

2 management nodes, 2 data nodes .. (config details below)

I can launch both management nodes but when I try connectiong to the management console on the 2nd node it fails with the following error

NDB Cluster Management Server. Version 5.1.11 (beta) Id: 2, Command port: 1186 Unable to connect to our own ndb_mgmd (Error -1) This is probably a bug.

I can connect from a remote node to both nodes and they give different outputs.

It seems the second node is in som kind of Identity crisis :)

Is this a known bug , or did I forget something in my setup ?

bash-3.00# ndb_mgm -c 172.16.32.101 -- NDB Cluster -- Management Client -- ndb_mgm> show Connected to Management Server at: 172.16.32.101:1186 Cluster Configuration

--------------------- [ndbd(NDB)] 2 node(s) id=3 (not connected, accepting connect from 172.16.32.7) id=4 (not connected, accepting connect from 172.16.32.107)

[ndb_mgmd(MGM)] 2 node(s) id=1 (not connected, accepting connect from 172.16.32.1) id=2 @172.16.32.101 (Version: 5.1.11)

[mysqld(API)] 3 node(s) id=5 (not connected, accepting connect from any host) id=6 (not connected, accepting connect from any host) id=7 (not connected, accepting connect from any host)

ndb_mgm> -bash-3.00# ndb_mgm -c 172.16.32.1 -- NDB Cluster -- Management Client -- ndb_mgm> show Connected to Management Server at: 172.16.32.1:1186 Cluster Configuration

--------------------- [ndbd(NDB)] 2 node(s) id=3 (not connected, accepting connect from 172.16.32.7) id=4 (not connected, accepting connect from 172.16.32.107)

[ndb_mgmd(MGM)] 2 node(s) id=1 @172.16.32.1 (Version: 5.1.11) id=2 (not connected, accepting connect from 172.16.32.101)

[mysqld(API)] 3 node(s) id=5 (not connected, accepting connect from any host) id=6 (not connected, accepting connect from any host) id=7 (not connected, accepting connect from any host)

[ndbd default] NoOfReplicas= 2

[mgm] ID=1 HostName= 172.16.32.1 [mgm] ID=2 Hostname= 172.16.32.101 [ndbd] ID=3 HeartbeatIntervalDbDb=600 HeartbeatIntervalDbApi=600 HostName= 172.16.32.7 DataDir: /var/lib/mysql/mysql-cluster/ DataMemory = 300M IndexMemory = 50M MaxNoOfConcurrentTransactions = 500 MaxNoOfConcurrentOperations = 250000 TimeBetweenWatchDogCheck = 40000 MaxNoOfOrderedIndexes = 27000 MaxNoOfTables = 9000 MaxNoOfAttributes = 25000

[ndbd] ID=4 HeartbeatIntervalDbDb=600 HeartbeatIntervalDbApi=600 HostName = 172.16.32.107 DataDir: /var/lib/mysql/mysql-cluster/ DataMemory = 300M IndexMemory = 50M MaxNoOfConcurrentTransactions = 500 MaxNoOfConcurrentOperations = 250000 TimeBetweenWatchDogCheck = 40000 MaxNoOfOrderedIndexes = 27000 MaxNoOfTables = 9000 MaxNoOfAttributes = 25000

[mysqld] [mysqld] [mysqld]

EOF

Also when starting the 2nd node I only get a message in the 1st node's log file stating

2006-07-17 12:43:31 [MgmSrvr] INFO -- Mgmt server state: nodeid 2 reserved for ip 172.16.32.101, m_reserved_nodes 0000000000000006.

But no further info on successful connects.

greetings