Bug #52039 | cluster restart through various node failures triggered by ndb_mgmd failure | ||
---|---|---|---|
Submitted: | 13 Mar 2010 23:28 | Modified: | 6 Jun 2010 11:52 |
Reporter: | Robert Klikics | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Linux (Debian 5.0) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | node ndb_mgmd failure telco-7.0.9b |
[13 Mar 2010 23:28]
Robert Klikics
[6 May 2010 11:52]
Jonas Oreland
Hi, I've analyzed the logs, i don't know how you measure that latency was up "2-5%" but from what i can see, it sure looks like some kind of (transient) network failure. I did find an incorrectly formated error message, ndbrequire for node 3, which turned out to be Bug #48852, fixed in 7.0.10. Unless you manage to reproduce this, or present some other information I think this bug will not move forward. Setting status 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".