MySQL Bugs: #77791: data node crash

Bug #77791	data node crash
Submitted:	21 Jul 2015 12:43	Modified:	28 Nov 2015 10:30
Reporter:	Zhengxiang Pan Pan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	mysql-cluster-gpl-7.4.6-linux-glibc2.5-x	OS:	Ubuntu
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
(gdb) bt
#0  Pgman::get_page_no_lirs (this=0x2e02810, jamBuf=0x7f85b3a508a8, signal=<optimized out>, ptr=..., page_req=...)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/pgman.cpp:1872
#1  0x0000000000457f73 in Pgman::get_page (this=0x7f85b3a22480, jamBuf=0x0, signal=0xe80cb1f8, ptr=..., page_req=...)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/pgman.cpp:1905
#2  0x000000000045813d in Page_cache_client::get_page (this=0x7f7f778ec9c0, signal=0x7f7f778edb80, req=..., flags=2306)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/pgman.cpp:2267
#3  0x000000000069f9e8 in Dbtup::retrieve_data_page (this=0x7f85ac16e010, signal=0x7f7f778edb80, req=..., regOperPtr=..., diskPagePtr=...)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp:589
#4  0x00000000006a12bb in Dbtup::execTUP_COMMITREQ (this=0x7f85ac16e010, signal=0x7f7f778edb80)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp:832
#5  0x000000000057ff48 in Dblqh::commitContinueAfterBlockedLab (this=0x2e3aaa0, signal=0x7f7f778edb80)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/SimulatedBlock.hpp:1169
#6  0x00000000005800f5 in Dblqh::localCommitLab (this=0x7f85b3a22480, signal=0x0)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:8644
#7  0x00000000005801fa in Dblqh::commitReqLab (this=0x2e3aaa0, signal=0x7f7f778edb80, gci_hi=<optimized out>, gci_lo=<optimized out>)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:8559
#8  0x0000000000580d99 in Dblqh::execPACKED_SIGNAL (this=0x2e3aaa0, signal=0x7f7f778edb80)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/blocks/dblqh/DblqhMain.cpp:3464
#9  0x0000000000767253 in executeFunction (f=<optimized out>, signal=<optimized out>, gsn=<optimized out>, this=<optimized out>)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/SimulatedBlock.hpp:1169
#10 executeFunction_async (signal=<optimized out>, gsn=45560, this=<optimized out>)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/SimulatedBlock.hpp:1140
#11 execute_signals (selfptr=0x7f85b3a46ac0, q=0x7f85b3a499c0, h=0x7f85b3a46ec0, r=0x7f85b3a50158, sig=0x7f7f778edb80, max_signals=100)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/mt.cpp:4151
#12 0x00000000007675e6 in run_job_buffers (selfptr=0x7f85b3a46ac0, sig=0x7f7f778edb80)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/mt.cpp:4252
#13 0x000000000076abfe in mt_job_thread_main (thr_arg=<optimized out>)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/kernel/vm/mt.cpp:4975
#14 0x000000000070e897 in ndb_thread_wrapper (_ss=0x2ea3c40)
    at /export/home/pb2/build/sb_0-14878975-1427910463.16/mysql-cluster-gpl-7.4.6/storage/ndb/src/common/portlib/NdbThread.c:202
#15 0x00007f85b557de9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#16 0x00007f85b468c8bd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#17 0x0000000000000000 in ?? ()

How to repeat:
The datanode crash while I am importing data from the mysqldump.  The data size is around 20millions rows

Hi,

Thank you for submitting the bug report but you did not provide enough data for the bug analysis. You have to collect all the logs (use ndb_error_log utility) and attach to the bug. 

It was most probably expected / designed behavior of miss configured cluster but until you provide more details I can only guess.

all best
Bogdan Kecman

I recalled I attempt to load the ndb report, but no way to file a button to submit. This UI is not nice

I loaded into  sftp.oracle.com:/support/incoming/ndb_error_report_20150721083726.tar.bz2

Hi,
I don't see enough in the logs to find out what exactly happened and how to reproduce the problem. Did you see this problem again or it was one off only?

all best
Bogdan Kecman

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