Bug #49027 | Management node disconnects unexpectedly when other mgmd is restarted | ||
---|---|---|---|
Submitted: | 24 Nov 2009 9:46 | Modified: | 7 Apr 2014 12:41 |
Reporter: | Oli Sennhauser | Email Updates: | |
Status: | Unsupported | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Any |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
Tags: | cluster, heartbeat, management, missed, MySQL, node, restart, warning |
[24 Nov 2009 9:46]
Oli Sennhauser
[24 Nov 2009 9:46]
Oli Sennhauser
config.ini
Attachment: config.ini (application/octet-stream, text), 668 bytes.
[24 Nov 2009 9:46]
Oli Sennhauser
Cluster log of 1st mgmd
Attachment: ndb_2_cluster.log (text/x-log), 22.91 KiB.
[27 Nov 2009 9:46]
Oli Sennhauser
* Have a cluster with 2 mgmd and 4 ndbd. * Connect to mgmd 1 * Restart mgmd 2: ndb_mgm> show Cluster Configuration --------------------- [ndbd(NDB)] 4 node(s) id=2 @127.0.0.1 (mysql-5.1.39 ndb-7.0.9, Nodegroup: 0, Master) id=3 @192.168.1.35 (mysql-5.1.39 ndb-7.0.9, Nodegroup: 0) id=4 @127.0.0.1 (mysql-5.1.39 ndb-7.0.9, Nodegroup: 1) id=5 @192.168.1.35 (mysql-5.1.39 ndb-7.0.9, Nodegroup: 1) [ndb_mgmd(MGM)] 2 node(s) id=101 @192.168.1.33 (mysql-5.1.39 ndb-7.0.9) id=102 @192.168.1.35 (mysql-5.1.39 ndb-7.0.9) [mysqld(API)] 5 node(s) id=6 (not connected, accepting connect from any host) id=7 (not connected, accepting connect from any host) id=8 (not connected, accepting connect from any host) id=9 (not connected, accepting connect from any host) id=10 (not connected, accepting connect from any host) ndb_mgm> 102 restart Shutting down MGM node 102 for restart Restart failed. * 0: No error * Executing: ndb_mgm_restart3
[27 Nov 2009 9:48]
Oli Sennhauser
config.ini which was used for reproduction
Attachment: config.ini (application/octet-stream, text), 797 bytes.
[27 Nov 2009 9:51]
Oli Sennhauser
Logfiles of all nodes
Attachment: cluster_log_files.tgz (application/x-gtar, text), 9.05 KiB.
[7 Apr 2014 12:41]
Magnus Blåudd
Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product you 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.