MySQL Forums
Forum List  »  NDB clusters

Using separate network for data nodes
Posted by: Brian Z
Date: December 03, 2006 11:21AM

Hi group,

I have a running 5.1.11 cluster working with 4 servers:
server1 - management, sql, data
server2 - sql, data
server3 - sql, data
server4 - sql, data

Each server has 4 gig ethernet cards. All communications are currently going over the same eth0 interface (eg. 172.16.100.0/24). eth1 (eg. 172.16.90.0/24) is connected to a private gig ethernet switch.

Changing config.ini to have the data nodes on the eth1 IP's results in the following:

# ndbd
error=2350
2006-12-03 12:11:24 [ndbd] INFO -- Error handler restarting system
2006-12-03 12:11:24 [ndbd] INFO -- Error handler shutdown completed - exiting
sphase=0
exit=-1

[root@lindb1 etc]# ndb_mgm
-- NDB Cluster -- Management Client --
ndb_mgm> show
Connected to Management Server at: 172.16.100.22:1186
Cluster Configuration
---------------------
[ndbd(NDB)] 4 node(s)
id=6 (not connected, accepting connect from 172.16.90.22)
id=7 @172.16.100.23 (Version: 5.1.11, Nodegroup: 0, Master)
id=8 @172.16.100.24 (Version: 5.1.11, Nodegroup: 1)
id=9 @172.16.100.25 (Version: 5.1.11, Nodegroup: 1)

[ndb_mgmd(MGM)] 1 node(s)
id=1 @172.16.100.22 (Version: 5.1.11)

[mysqld(API)] 4 node(s)
id=2 @172.16.100.22 (Version: 5.1.11)
id=3 @172.16.100.23 (Version: 5.1.11)
id=4 @172.16.100.24 (Version: 5.1.11)
id=5 @172.16.100.25 (Version: 5.1.11)

I'm guessing ndbd is binding to the first IP it sees? I know there is also a TCP section available for config.ini, but the manual states this is only for direct connections. I tried it anyways, but ndb_mgmd won't start with it. I suspect this is a red herring anyways.

How do I configure data node traffic to go over eth1 on all the nodes?


Brian

Options: ReplyQuote


Subject
Views
Written By
Posted
Using separate network for data nodes
1746
December 03, 2006 11:21AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.