Bug #12952 [NOTE] in mysqld error log from graceful cluster shutdown may misslead customer
Submitted: 2 Sep 2005 15:51 Modified: 2 Sep 2005 16:11
Reporter: Jonathan Miller Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:mysql-5.1 OS:Linux (Linux)
Assigned to: CPU Architecture:Any
Tags: 5.1.2
Triage: Triaged: D5 (Feature request)

[2 Sep 2005 15:51] Jonathan Miller
Description:
050902 17:13:02 [Note] NDB Binlog: cluster failure for atae/dcacache.
050902 17:13:02 [Note] NDB Binlog: cluster failure for cluster_replication/apply_status.
Management server closed connection early. It is probably being shut down (or has crashed). We will retry the connection.
Management server closed connection early. It is probably being shut down (or has crashed). We will retry the connection.

How to repeat:
shutdown cluster and leave mysqld running.

Suggested fix:
We should have a message that tell the customer that if they did a graceful shutdown of the cluster to ignore these messages.

In addition, we should create a way for the cluster to comunicate to mysqld that a shutdown of the cluster has been issued by the administrator and not the abitrator. I will open a work log for this.
[2 Sep 2005 16:06] Sloan Childers
Thank you for your interest in the MySQL graphical administration tools.
We recommend that you use our MySQL Administrator and MySQL Query
Browser.  The MySQLGUI and MySQL Command Center legacy products are
deprecated, and we are no longer maintaining those projects.

For more information on MySQL Administrator, see:
http://www.mysql.com/products/administrator/