MySQL Bugs: #54746: Mysql Cluster on public ips

Bug #54746	Mysql Cluster on public ips
Submitted:	23 Jun 2010 16:01	Modified:	25 Jul 2010 14:39
Reporter:	Dragos Gabriel Iancu	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-5.1-telco-7.0	OS:	Linux (Ubuntu and CentOS)
Assigned to:		CPU Architecture:	Any
Tags:	cluster, public ip

Description:
In the FAQ of mysql cluster you say :

[MySQL Cluster is intended to be used in a high-bandwidth environment, with computers connecting via TCP/IP. Its performance depends directly upon the connection speed between the cluster's computers...]

We are trying to make this work for 1 week, read all documentations, tryed centos and ubuntu distro.

Our management server show this:
-- 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 195.66.x.122)
id=3    @193.230.x.214  (mysql-5.1.39 ndb-7.0.9, starting, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @195.66.x.36  (mysql-5.1.39 ndb-7.0.9)

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

When we check the status of the node 3 it is in phase 0 of starting.

How to repeat:
the bug appear when we install mysql cluster on ubuntu/centos servers located in different locations with different public ips.

Looks as if the data nodes can't see each other (firewall?)

Running a cluster installation with nodes in different locations
and on public IP interfaces is not a good idea anyway:

* network latency is key here, so even with high bandwidth between the locations latency delays can become a real issue
* there is no authentication mechanism in the management node, so with it listening on a public IP anyone can e.g. shut the cluster down ...

The authentication issue can be worked around by e.g. proper firewall rules,
the latency issues from nodes in different locations can only be overcome by faster-than-light communication though ...

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".