MySQL Bugs: #6683: It's possible to STOP ndb_mgmd but mgm client doesn't get disconnected

Bug #6683	It's possible to STOP ndb_mgmd but mgm client doesn't get disconnected
Submitted:	17 Nov 2004 16:04	Modified:	30 Nov 2004 7:56
Reporter:	Arjen Lentz	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	Linux (Linux)
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
I can STOP a ndb_mgmd node from the mgm client.
However, the client does not get disconnected. It reports errors but also garbage.

I see that a STOP on a mgmd node actually stops the process (it's gone from ps xa) so perhaps it can be useful. But then the situation needs to be handled.

How to repeat:
NDB> 1 stop
Executing STOP on node 1.
Node 1 has shutdown.

NDB> all status
Unable get status from management server
*  1008: Illegal node status
*        Mpñÿ¿Øîÿ¿ð<ïÿ¿Øîÿ¿ñÿ¿8<ïÿ¿ñÿ¿2èèñÿ¿ñÿ¿=Xñÿ¿

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

In newer version connect/disconnect between ndb_mgm and ndb_mgmd is handled sligtly differently.

I should not disconnect.  You can connect to different clusters with the same management client...