MySQL Bugs: #17186: rpl_ndb

Bug #17186	rpl_ndb_blob.test hangs
Submitted:	7 Feb 2006 11:26	Modified:	14 Apr 2006 5:41
Reporter:	Ingo Strüwing	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.7	OS:	Linux (Linux, kernel 2.6.15)
Assigned to:	Pekka Nousiainen	CPU Architecture:	Any

Description:
rpl_ndb_blob.test hangs occasionally.

I formerly noticed hangs with rpl_ndb_idempotent, rpl_ndb_load, and rpl_ndb_multi, if I remeber correctly. All of these hangs happened when multiple test suites ran in parallel. I believed this could be because of resource conflicts and parallel test runs are not supported yet.

But this time I am totally sure that just that single one test suite ran alone. Thus it's time to report it as a bug. I collected all information, which I deemed important into a file, which I will attach to the bug report.

[off topic]
When looking at the other hangs (parallel running test suites) I saw core files, which is not the case with the current hang. A quick check with gdb showed an assert problem in the manager, I believe to remember. There is a good chance that I could repeat a hang with parallel tests. Just tell me if you need my help and tell me, what information you need.

How to repeat:
BUILD/compile-pentium-debug-max
Run the test suite again and again on a Linux kernel 2.6.15 and hope that it happens again...

Forensic information

Attachment: rpl_ndb_bug_report.txt (text/plain), 82.52 KiB.

Forensic information #2

Attachment: rpl_ndb_blob_report-2.txt (text/plain), 158.63 KiB.

Forensic information #2 binlog test 1

Attachment: rpl_ndb_blob_report-binlog-1 (application/octet-stream, text), 10.04 KiB.

Forensic information #2 binlog test 2

Attachment: rpl_ndb_blob_report-binlog-2 (application/octet-stream, text), 9.98 KiB.

It happened again. This time with two tests running in parallel. test1 seems to have ended correctly (All 457 tests were successful). test2 hang in rpl_ndb_blob.

This time I found a core file. But in the test1 directory tree. Anyway basic core file analysis is contained in the attached file. I added the binlogs from both tests. May it be useful.

Forensic information #3 (ndb_minmax)

Attachment: ndb_minmax_report-1.txt (text/plain), 158.25 KiB.

Forensic information #3 (ndb_minmax) binlog test 1

Attachment: rpl_ndb_blob_report-2-binlog-1 (application/octet-stream, text), 10.04 KiB.

Forensic information #3 (ndb_minmax) binlog test2

Attachment: ndb_minmax_report-1-binlog-2 (application/octet-stream, text), 1.59 KiB.

Forensic information #4 (rpl_ndb_UUID)

Attachment: rpl_ndb_UUID_report-1.txt (text/plain), 156.47 KiB.

Forensic information #4 (rpl_ndb_UUID) binlog test 1

Attachment: rpl_ndb_UUID_report-1-binlog-1 (application/octet-stream, text), 10.04 KiB.

Forensic information #4 (rpl_ndb_UUID) binlog test 2

Attachment: rpl_ndb_UUID_report-1-binlog-2 (application/octet-stream, text), 1.12 KiB.

Added forensics for another hang.

Forensic information #5

Attachment: ndb_hang-1.txt (text/plain), 69.57 KiB.

Forensic information #5 binlogs

Attachment: ndb_hang-1-binlogs.tgz (application/x-gtar, text), 17.54 KiB.

Forensic information #6

Attachment: ndb_hang-2.txt (text/plain), 88.86 KiB.

Forensic information #6 binlogs

Attachment: ndb_hang-2-binlogs.tgz (application/x-gtar, text), 1.38 KiB.

Added more forensic information.