MySQL Bugs: #33742: NDBD node crashes when unable to create backup (undescriptive error)

Bug #33742	NDBD node crashes when unable to create backup (undescriptive error)
Submitted:	8 Jan 2008 16:25	Modified:	8 Feb 2008 16:30
Reporter:	Jeffrey R	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.22	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	Backup, cluster, MySQL, ndb, ndbd

Description:
Running "START BACKUP" fails with very undescriptive message.

(also note a type where it says "Backup abortet")

----------
ndb_mgm> START BACKUP
Waiting for completed, this may take several minutes
Node 4: Backup 152 started from node 2
Backup failed
* 3001: Could not start backup
* Backup abortet due to node failure: Permanent error: Internal error
ndb_mgm> Node 4: Forced node shutdown completed. Caused by error 2341: 'Internal program error (failed ndbrequire)(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.
----------

It became impossible to create backups after creating a ~1,000,000 entries on 10 tables and then removing them, possibly the undo log is too large.

Seems to be related to a another recently submitted bug:
http://bugs.mysql.com/bug.php?id=31920

Although I believe disk space is not the issue here as `df -h` shows that their should be plenty of space.

--------------
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 33G 18G 14G 57% /
--------------

ndb fs on node uses about 14GB including UNDO and TABLE space logs.

--------------
du -h --max-depth=1 ndb_4_fs/
257M ndb_4_fs/D9
3.6M ndb_4_fs/D1
257M ndb_4_fs/D8
200M ndb_4_fs/LCP
3.6M ndb_4_fs/D2
257M ndb_4_fs/D11
257M ndb_4_fs/D10
14G ndb_4_fs/
--------------

How to repeat:
Create tablespace and undo logs. Apply these to a disk storage disk, create 1,000,000 entries (including BLOB column types). Remove entries. Attempt to run "START BACKUP" via ndb_mgm.

Suggested fix:
More descriptive error message for better debugging.

Please provide the ndb_4_error.log and ndb_4_trace* files from node four and the general cluster log from the management node, too.

Includes config.ini, trace.log, ndb error log, undolog file query from INFORMATION_SCHEMA.FILES

Attachment: ndb_4_error_2341.zip (application/x-zip-compressed, text), 35.94 KiB.

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