Bug #55150 Assertion `gci_ops && (op->getGCI() == gci_ops->m_gci)' while loading data
Submitted: 10 Jul 2010 6:45
Reporter: Sveta Smirnova Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: CPU Architecture:Any
Triage: Triaged: D2 (Serious) / R6 (Needs Assessment) / E6 (Needs Assessment)

[10 Jul 2010 6:45] Sveta Smirnova
Description:
While loading data into NDB table I got Assertion `gci_ops && (op->getGCI() == gci_ops->m_gci)' 

From error log:

mysqld: NdbEventOperationImpl.cpp:1375: NdbEventOperation* NdbEventBuffer::nextEvent(): Assertion `gci_ops && (op->getGCI() == gci_ops->m_gci)' failed.
100710  8:38:09 - mysqld got signal 6 ;
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=8384512
read_buffer_size=131072
max_used_connections=0
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 = 338331 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xdd538d8
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...
stack_bottom = 0x450ecfd8 thread_stack 0x40000
/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//libexec/mysqld(my_print_stacktrace+0x35)[0xb4edb4]
/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//libexec/mysqld(handle_segfault+0x288)[0x6b1a52]
/lib64/libpthread.so.0[0x3429e0dd40]
/lib64/libc.so.6(gsignal+0x35)[0x3429230015]
/lib64/libc.so.6(abort+0x110)[0x3429231980]
/lib64/libc.so.6(__assert_fail+0xf6)[0x3429229726]
/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//libexec/mysqld(_ZN14NdbEventBuffer9nextEventEv+0x28d)[0xabe92f]
/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//libexec/mysqld(_ZN3Ndb9nextEventEv+0x1c)[0xa8c004]
/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//libexec/mysqld(ndb_binlog_thread_func+0x137f)[0x93a6be]
/lib64/libpthread.so.0[0x3429e061b5]
/lib64/libc.so.6(clone+0x6d)[0x34292cd39d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
1. Start cluster with parameters indicated in bug #38264, but with
DataMemory=120M
IndexMemory=130M
and 2 SQL nodes.
2. Connect to one of mysqld and execute queries: create table t1(f1 varchar(255)) engine = ndb; insert into t1 values(md5('fds');
3. insert into t1 select * from t1;
4. Run step 3 until another mysqld crashes:

mysql>  insert into t1 select * from t1; insert into t1 select * from t1; insert into t1 select * from t1; insert into t1 select * from t1; insert into t1 select * from t1;
Query OK, 131072 rows affected (2 min 34.74 sec)
Records: 131072  Duplicates: 0  Warnings: 0

ERROR 1297 (HY000): Got temporary error 4010 'Node failure caused abort of transaction' from NDBCLUSTER
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
mysql> select count(*) from t1;
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
mysql> select * from t1 limit 1;
ERROR 1296 (HY000): Got error 157 'Unknown error code' from NDBCLUSTER
mysql> \q
Bye
[2]+  Exit 1                  $BASEDIR/libexec/mysqld --defaults-file=etc/ndb_node_api2.cfg
5. Examine mysqld error log