Bug #81360 there is memory crash issue in mysql-5.6.27 ndb-7.4.8
Submitted: 10 May 2016 4:34 Modified: 7 Jun 2016 11:41
Reporter: Jingyu Hu Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:7.4.8 OS:CentOS (CentOS 7)
Assigned to: MySQL Verification Team CPU Architecture:Any

[10 May 2016 4:34] Jingyu Hu
This morning, our mysql cluster ndbd is crashed, i cat ndb_3_error.log, i tells:
Current byte-offset of file-pointer is: 568

Time: Tuesday 10 May 2016 - 01:23:52
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming error or missing error message, please report a bug)
Error: 2341
Error data: DbtupTrigger.cpp
Error object: DBTUP (Line: 2200) 0x00000002
Program: ndbd
Pid: 22777
Version: mysql-5.6.27 ndb-7.4.8
Trace: /usr/local/mysql/data/ndb_3_trace.log.1 [t1..t1]

please check ndb_error_report_20160510122736.tar.bz2 for details.

How to repeat:
It happened once today.
[10 May 2016 4:40] Jingyu Hu
The files collected by ndb_error_reporter

Attachment: ndb_error_report_20160510122736.tar.bz2 (application/octet-stream, text), 303.68 KiB.

[25 May 2016 14:18] MySQL Verification Team

This crash happened during LCP. I can't reproduce this but looking at the logs I don't see anything specific. Can you check your system log if there are any hw errors reported in that period (storage/memory/cpu errors)?

Any specific test you were running when this happened?

I see that only node 3 crashed and then restarted normally, but later on you did a full cluster restart (09:47), any reason for this? Were you experiencing problems after node3 restarted after reported error?

Bogdan Kecman
[7 Jun 2016 11:30] Jingyu Hu
Hi Kecman,

There is no specific test running when this happened.
When this issue happened, our system is not in busy state.

Now i upgrade MySQL Cluster to "mysql-5.6.29 ndb-7.4.11", this issue does not happened till now.

Best Regards,
Hu Jingyu
[7 Jun 2016 11:41] MySQL Verification Team

So you are saying after upgrade to 7.4.11 you are not seeing this problem any more?

best regards
Bogdan Kecman