Bug #83424 | ndbmtd crash | ||
---|---|---|---|
Submitted: | 18 Oct 2016 9:58 | Modified: | 19 Nov 2016 23:10 |
Reporter: | Marco Michelino | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.6.17 ndb-7.3.5 | OS: | CentOS |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[18 Oct 2016 9:58]
Marco Michelino
[19 Oct 2016 23:10]
MySQL Verification Team
Hi, With only a trace file I can't get all the info on what is going on at the cluster. Please upgrade a full log (you can generate it with ndb_error_reporter tool). You can also think about upgrading to the latest version (7.4.13 for e.g. or at least 7.3.15) as 7.3.5 is *very* old. Thanks Bogdan Kecman
[20 Nov 2016 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".