www.infinidb.org

Hi

The environment :

Kernel : Linux mysql-mxxx.xxxx 2.6.32.3-sdf117-core2-64 #1 SMP Fri Jan 15 10:50:12 CET 2010 x86_64 Intel(R) Xeon(R) CPU E5540 @ 2.53GHz GenuineIntel GNU/Linux

InfiniDB : 1.0.6 final binary

Operating system : Gentoo Linux

Mem: 32236 17793 14442 0 80 484

The process :

We have a script who, drop the table if the table exist, and recreate it.
I import the table from a .csv (around 10Go)
Some times, the drop table in InfiniDB don't manage to drop the table, and InfiniDB don't give back the hand after the drop table.

I'm not able to say why infiniDB don't want to drop the table, but the bug is here.

My Process success around a week every day, and sometime the issues is here.

Do you have any idea ?

I copy / paste this from my shell (where infiniDB was started) when InfiniDB crash, but i don't know if this copy/paste is linked with my InfiniDB crash.
Perhaps it can help !

7ff694d0e000-7ff694d0f000 ---p 00000000 00:00 0
7ff694d0f000-7ff695d13000 rw-p 00000000 00:00 0 *** glibc detected *** PrimProc: double free or corruption (!prev): 0x0000000000ddcd00 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f718537f0bd]
/lib/libc.so.6(cfree+0x76)[0x7f7185380a76]
/usr/local/Calpont/lib/libmessageqcpp.so.1(_ZN11messageqcpp10ByteStreamD1Ev+0x20)[0x7f71870d50d0]
PrimProc[0x468e1a]
PrimProc[0x448f5d]
PrimProc[0x453662]
PrimProc[0x48b71f]
PrimProc[0x48bd46]
PrimProc[0x48043d]
PrimProc[0x4898e2]
/usr/local/Calpont/lib/libboost_idb.so.1(thread_proxy+0x76)[0x7f7186a24336]
/lib/libpthread.so.0[0x7f7186422097]
/lib/libc.so.6(clone+0x6d)[0x7f71853d577d]
======= Memory map: ========
00400000-00501000 r-xp 00000000 fd:00 6431034 /home/calpont-infinidb-1.0.6/bin/PrimProc
00701000-00703000 rw-p 00101000 fd:00 6431034 /home/calpont-infinidb-1.0.6/bin/PrimProc
00703000-0639c000 rw-p 00000000 00:00 0 [heap]
7f6c117f3000-7f6c117f4000 ---p 00000000 00:00 0
7f6c117f4000-7f6c11ff4000 rw-p 00000000 00:00 0
7f6c11ff4000-7f6c11ff5000 ---p 00000000 00:00 0

Hi Bragon,

This may be an existing bug and I am cehcking with our staff on that. Meanwhile, is there anything in the log files (/var/log/Calpont) or the error file (/usr/local/Calpont/mysql/db/*.err) generated when this happens?

If so, please email them to dstokes at Calpont.com

Hi Dave

I have this in the .err :

======
100629 11:28:14 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=11875136
read_buffer_size=4194304
max_used_connections=48
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1250157 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
=======

Any idea ?

It is hard to guess what is going on from the information. Are their any locks on the table before the drop/create or any other access on the tables? If you send me a copy of the 'show create table x' output, I will try to re-create.

We noticed that you are running on an older version, 1.0.6. There have been a number of fixes applied to the software since that version. If you are able, could you update to one of our later versions, 1.5+ and see if the problem still exist.

If so, could you attach 'gdb' to the PrimProc and perform a backtrace to capture the outage. And if possible, provided any logs that were updated from /var/log/Calpont/.

Thanks

@davidhill
I'm using 1.0.6 because it's tagged as stable.
1.5+ is just a Release Candidate i guess.

there are no problem to run a 1.5+ in production server ?

@davestockes

show create table x
Do you want this output during the InfiniDB can't drop the table ?