MySQL Bugs: #29336: mgmd could warn user if mgmd and ndbd is on the same node

Bug #29336	mgmd could warn user if mgmd and ndbd is on the same node
Submitted:	25 Jun 2007 13:52	Modified:	26 Jun 2009 17:16
Reporter:	Oli Sennhauser	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S4 (Feature request)
Version:	mysql-5.1	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
There is a recommendation that one should not locate a mgmd on the same server as a ndbd.
This could be checked during startup and noticed in the error log file as a warning.

How to repeat:
Warning: mgm node ... is located on the same server as data node ... which is not recommmended.

Thank you for a reasonable feature request.

I believe it does this. Can you check to see if this is still valid?

Hi Jonathan,

I did the tests today with 6.3.20 and my config.ini is as follows:

[NDB_MGMD]
Id                            = 1
HostName                      = <host_name>

[NDBD]
Id                            = 10
HostName                      = <host_name>

[NDBD]
Id                            = 11
HostName                      = <host_name>

Here is the outcome:

mgmd          ndbd_10       ndbd_11       comment     observation
-----------------------------------------------------------------
localhost     localhost     localhost                 NO warning
192.168.1.33  192.168.1.33  192.168.1.33  local IP    Resolves IP to localhost -> NO warning
192.168.1.33  192.168.1.33  192.168.1.35              Warning on the console but NOT in the cluster.log

What further confuses me is that the local IP is translated into localhost (and then treated as localhost). This is NOT what I expect (for example ping does not behave like this).

My expectation is in:

case 1: localhost cluster can make sense. So possibly no warning but a NOTE in cluster log?
case 2: NO resolution to localhost and warning on console and cluster log
case 3: warning on console AND cluster log.

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".