Bug #51108 | mysqld hangs after a node has killed during node restart after a GCP stop error | ||
---|---|---|---|
Submitted: | 11 Feb 2010 15:14 | Modified: | 9 Jan 2015 16:40 |
Reporter: | Robert Klikics | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.1-telco-7.0 | OS: | Linux (Debian 5.0) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | node killed gcp stop error mysqld hang, telco-7.0.9b |
[11 Feb 2010 15:14]
Robert Klikics
[6 May 2010 12:56]
Jonas Oreland
Hi, One known problem is that when a node fails, if a local-checkpoint is ongoing, it may not reconnect to cluster until some specific part of the checkpoint has been completed, this manifest it self, by that when the datanode restarts it will get "Could not alloc node", there is btw a bug/feature-request open to improve that message in "http://bugs.mysql.com/bug.php?id=52253" as for mysqld problems, i can find nothing in cluster logs etc, mysqld.err is missing to analyze any such problems. Setting this to need feedback /Jonas
[6 Jun 2010 23:00]
Bugs System
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".
[14 Jan 2012 4:31]
umapathi b
I too got the same error ..ndbd process is not running on one data node ..still the data is being updated on the failed node and it is updated on the second node . But I don't know if I restart the failed node ..what happens ..Plz help me in this regard how to resolve this .. Thanks, Umapathi umapathi.b@gmail.com