Bug #69959 | unable to start data node | ||
---|---|---|---|
Submitted: | 8 Aug 2013 3:56 | Modified: | 8 Feb 2014 4:59 |
Reporter: | Firzen Le | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 7.3.2 | OS: | Linux (centos 5.x) |
Assigned to: | CPU Architecture: | Any |
[8 Aug 2013 3:56]
Firzen Le
[8 Aug 2013 8:07]
Hartmut Holzgraefe
Would be interesting to see a core dump for this ... But if your node was down for several days already then doing an --initial restart doesn't harm, its local checkpoints will be so out of date by now that it would do a full sync anyway ...
[10 Aug 2013 3:59]
Firzen Le
Hi Hartmut, Thanks for replying. I'm gonna try to enable OS's core dump file then paste it in here. By the way, may I ask if one day I have to use ndbd --initial for all data node, have I got any chance to get my data back?
[10 Aug 2013 6:27]
Hartmut Holzgraefe
If you do a full initial restart ... well, better have a recent backup that you can restore from then, and binlogs enabled on mysqld nodes so that you can do point-in-time recovery from these for the span between time of the backup and time when cluster stopped working ...
[8 Jan 2014 4:59]
MySQL Verification Team
Hello Firzen, Thank you for the report. I couldn't reproduce the reported issue. Is this issue still repeatable(with latest GA 7.3.3)? Also, could you please attach the cluster logs? Preferably using the ndb_error_reporter utility: http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-programs-ndb-error-reporter.html Thanks, Umesh
[9 Feb 2014 1: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".