Bug #74355 BACKUP error caused whole cluster shutdown

• Submitted: 13 Oct 2014 11:23
• Modified: 7 Jan 2016 0:20
• Reporter: Сергей Кукуев
• Status: No Feedback
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S2 (Serious)
• Version: 7.3.7
• OS: Linux (2.6.39-200.24.1.el6uek.x86_64)
• Assigned to: MySQL Verification Team
• CPU Architecture: Any
• Tags: Backup, node, shutdown

[13 Oct 2014 11:23] Сергей Кукуев

Description:
Time: Friday 10 October 2014 - 15:53:34
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: Backup.cpp
Error object: BACKUP (Line: 5426) 0x00000002
Program: ndbmtd
Pid: 53320 thr: 3
Version: mysql-5.6.17 ndb-7.3.5
Trace: /opt/mysql/ndb_5_trace.log.1 [t1..t10]
***EOM***

How to repeat:
I don't know

[13 Oct 2014 11:26] Сергей Кукуев

uploaded ndb_error_report_20141013145706.tar.bz2 at /support/incoming

[24 Dec 2014 14:46] Сергей Кукуев

Hi!

Is there any progress on this bug?

We've faced with this buge once again.
Seemed that the cause of backup error is that one data node filesystem was full. But why it crashed whole cluster?

[24 Dec 2014 14:49] Сергей Кукуев

uploaded mysql-bug-74355-ndb_error_report_20141224182603.tar.bz at /support/incoming

[29 Sep 2015 6:03] Hendrik Woltersdorf

"Me too".
I experienced the same problem:

Current byte-offset of file-pointer is: 568

Time: Tuesday 29 September 2015 - 02:47:34
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: Backup.cpp
Error object: BACKUP (Line: 722) 0x00000006
Program: ndbmtd
Pid: 19931 thr: 2
Version: mysql-5.6.21 ndb-7.3.7
Trace: /db-data/mysqlcluster/ndb_10_trace.log.1 [t1..t11]
***EOM***

[7 Dec 2015 0:20] MySQL Verification Team

Hi Sergei,

I cannot reproduce this bug and our system, unfortunately, (for security reasons) does not keep files on the server long enough so the log files you uploaded are no longer available. 

If you can reproduce this bug, please update the report with procedure and new log files

kind regards
Bogdan Kecman

[7 Jan 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".