Bug #80867 | MySQL Cluster Crashed | ||
---|---|---|---|
Submitted: | 28 Mar 2016 12:17 | Modified: | 4 May 2016 5:01 |
Reporter: | Serhat Demircan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S1 (Critical) |
Version: | 7.4.10 | OS: | Debian (Wheezy) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | ndbcluster |
[28 Mar 2016 12:17]
Serhat Demircan
[28 Mar 2016 23:07]
Serhat Demircan
- Stop data node X - Start data node X After data node X reached started state this error occured. But this does not happen all times. Most of time i can restart all nodes for maintenance without a problem.
[29 Mar 2016 0:23]
MySQL Verification Team
Hi Serhat, You said you can't reproduce and then you said "it does not happen every time" so can you please clarify did you see this problem only once or you see this problem "often but not always" when you start your cluster? Can you, please, upload the whole ndb_error_log result with all the logs as just traces don't show the whole picture kind regards Bogdan Kecman
[29 Mar 2016 5:24]
Serhat Demircan
Hi Bogdan, Not only once. I see this problem often but not always when restarting data nodes. For example It happened again after reported this one. Uploaded ndb_out.log, ndb_error.log and ndb_trace.log.
[4 May 2016 5:01]
MySQL Verification Team
Hi Serhat, would be better if you uploaded the whole ndb_error_reporter collection of logs and not only the single crash but anyhow looking at the logs you provided I'd say that this is not a bug but a missconfigured system. It looks like your system is overloaded and crashing. What is your cpu usage on all datanodes when you encounter this problem? Also what is your IO usage on all datanodes when you encounter this problem? I cannot reproduce crash in the place you have it in the log you provided but you can see watchdog complaining kind regards Bogdan