InnoDB: unknown error code 1000 | Assertion failure in row_mysql_handle_errors in file row0mysql.cc line 686 | Now in row0mysql.cc line 688

Bug #1200502 reported by Alexey Bychko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Triaged
Medium
Laurynas Biveinis
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Won't Fix
Low
Unassigned

Bug Description

Thread 1 (Thread 0x7ffdcc48e700 (LWP 21757)):
+bt
#0 0x00007ffdd28ac69c in pthread_kill () from /lib64/libpthread.so.0
#1 0x000000000066365e in handle_fatal_signal (sig=6) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/signal_handler.cc:251
#2 <signal handler called>
#3 0x00007ffdd0f648a5 in raise () from /lib64/libc.so.6
#4 0x00007ffdd0f66085 in abort () from /lib64/libc.so.6
#5 0x0000000000981597 in row_mysql_handle_errors (new_err=0x7ffdcc48bfec, trx=0x7ffd3c0103c0, thr=<optimized out>, savept=<optimized out>) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/storage/innobase/row/row0mysql.cc:686
#6 0x0000000000984a80 in row_insert_for_mysql (mysql_rec=<optimized out>, prebuilt=<optimized out>) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/storage/innobase/row/row0mysql.cc:1325
#7 0x00000000008f8398 in ha_innobase::write_row (this=0x7ffd0c00c140, record=0x7ffd0c00b890 "\357\377") at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/storage/innobase/handler/ha_innodb.cc:6921
#8 0x00000000005af0fb in handler::ha_write_row (this=0x7ffd0c00c140, buf=0x7ffd0c00b890 "\357\377") at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/handler.cc:7419
#9 0x00000000006c68c0 in write_record (thd=0x3764f30, table=0x7ffd0c008890, info=0x7ffdcc48c3b0, update=0x7ffdcc48c330) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_insert.cc:1622
#10 0x00000000006cde07 in mysql_insert (thd=0x3764f30, table_list=0x7ffd3c004e58, fields=..., values_list=..., update_fields=..., update_values=..., duplic=DUP_UPDATE, ignore=false) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_insert.cc:1027
#11 0x00000000006e25d9 in mysql_execute_command (thd=0x3764f30) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_parse.cc:3647
#12 0x00000000006e6098 in mysql_parse (thd=0x3764f30, rawbuf=<optimized out>, length=58094280, parser_state=<optimized out>) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_parse.cc:6477
#13 0x00000000006e6f3c in dispatch_command (command=COM_QUERY, thd=0x3764f30, packet=0x3768e91 "INSERT DELAYED INTO `table500_innodb_compressed` ( `c17` ) VALUES ( LOAD_FILE('/sdd/randgen/data/earth2kb.jpg') ) ON DUPLICATE KEY UPDATE `c8` = '20040403224516.037925'", packet_length=169) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_parse.cc:1374
#14 0x00000000006b4c0f in do_handle_one_connection (thd_arg=<optimized out>) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_connect.cc:1615
#15 0x00000000006b4ce7 in handle_one_connection (arg=0x3764f30) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/sql/sql_connect.cc:1526
#16 0x0000000000ab89f9 in pfs_spawn_thread (arg=0x37205b0) at /bzr/5.6_opt/Percona-Server-5.6.12-rc60.4/storage/perfschema/pfs.cc:1855
#17 0x00007ffdd28a7851 in start_thread () from /lib64/libpthread.so.0
#18 0x00007ffdd101a90d in clone () from /lib64/libc.so.6

Revision history for this message
Alexey Bychko (abychko) wrote :
Revision history for this message
Alexey Bychko (abychko) wrote :
Revision history for this message
Alexey Bychko (abychko) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :

Query (7ffd3c004bd0): INSERT DELAYED INTO `table500_innodb_compressed` ( `c17` ) VALUES ( LOAD_FILE('/sdd/randgen/data/earth2kb.jpg') ) ON DUPLICATE KEY UPDATE `c8` = '20040403224516.037925'

summary: - Assertion failure in thread 140728030783232 in file row0mysql.cc line
- 686
+ InnoDB: unknown error code 1000 | Assertion failure in file row0mysql.cc
+ line 686
Revision history for this message
Roel Van de Paar (roel11) wrote : Re: InnoDB: unknown error code 1000 | Assertion failure in file row0mysql.cc line 686

Alexey, do you have the run command? (~/percona_qa/startup <trialnr> in workdir, then cat cmd<trialnr>)

summary: - InnoDB: unknown error code 1000 | Assertion failure in file row0mysql.cc
- line 686
+ InnoDB: unknown error code 1000 | Assertion failure in
+ row_mysql_handle_errors in file row0mysql.cc line 686
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote : Re: InnoDB: unknown error code 1000 | Assertion failure in row_mysql_handle_errors in file row0mysql.cc line 686

err code 1000 is DB_FAIL.

Unless fake changes were enabled for the session (is the core saved?), this is almost guaranteed upstream bug.

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Assigning to Alexey re. core file.

tags: added: upstream
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Whether this bug is upstream or not depends on whether the fake changes were enabled for the run, so this is unclear yet.

tags: removed: upstream
Revision history for this message
Roel Van de Paar (roel11) wrote :

Since QA Branch rev 428 (Percona-Server-5.6.13-rc60.5-428-debug-valgrind.Linux.x86_64), this assertion is now seen regularly on LOAD DATA INFILE queries.

2013-09-11 07:16:52 22089 [Note] /ssd/Percona-Server-5.6.13-rc60.5-428.Linux.x86_64/bin/mysqld: ready for connections.
Version: '5.6.13-rc60.5-log' socket: '/ssd//349312/current1_6/tmp/master.sock' port: 13100 Percona Server with XtraDB (GPL), Release rc60.5, Revision 428
InnoDB: unknown error code 1000 <---------- (!)
2013-09-11 07:17:56 7fd1dd326700 InnoDB: Assertion failure in thread 140539335960320 in file row0mysql.cc line 686
[...]
Query (7fd1cc00c160): LOAD DATA INFILE '/ssd//349312/tmp/gentest22176.tmp' INTO TABLE `table100_innodb_default_key_c1_parts_2`
Connection ID (thread ID): 9
Status: NOT_KILLED

Revision history for this message
Roel Van de Paar (roel11) wrote :

RQG @ 904 <email address hidden>

Revision history for this message
Roel Van de Paar (roel11) wrote :
tags: added: qablock
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :

In correction of #9, #9-#15 relate to Percona-Server-5.6.13-rc60.5-428.Linux.x86_64 (optimized).

There was also Percona-Server-5.6.13-rc60.5-428-debug-valgrind.Linux.x86_64 issue(s), so logging that one below.

Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
tags: added: fake-changes
Revision history for this message
Roel Van de Paar (roel11) wrote :
tags: added: 56qual
tags: removed: 56qual
Revision history for this message
Roel Van de Paar (roel11) wrote :

Line number has changed

InnoDB: unknown error code 1000
2014-10-04 20:47:15 7f8e7ca07700 InnoDB: Assertion failure in thread 140249952974592 in file row0mysql.cc line 688

summary: InnoDB: unknown error code 1000 | Assertion failure in
- row_mysql_handle_errors in file row0mysql.cc line 686
+ row_mysql_handle_errors in file row0mysql.cc line 686 | Now in
+ row0mysql.cc line 688
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Ramesh Sivaraman (rameshvs02) wrote :

*** Got testcase (only on debug build)

DROP DATABASE test;CREATE DATABASE test;USE test;
CREATE TABLE t1(a DATE);
insert into t1 values(0xA141);
SET innodb_fake_changes=1;
set global innodb_limit_optimistic_insert_debug=1;
INSERT INTO t1 VALUES('����'),('����'),('����'),('����'),('����'),('����');

Revision history for this message
Ramesh Sivaraman (rameshvs02) wrote :
Download full text (3.9 KiB)

*** GDB info (comment #23)

#0 0x00007f8422476771 in pthread_kill () from /lib64/libpthread.so.0
#1 0x0000000000ab7586 in my_write_core (sig=6) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/mysys/stacktrace.c:422
#2 0x000000000072f9ff in handle_fatal_signal (sig=6) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/signal_handler.cc:236
#3 <signal handler called>
#4 0x00007f842107a5c9 in raise () from /lib64/libc.so.6
#5 0x00007f842107bcd8 in abort () from /lib64/libc.so.6
#6 0x0000000000bd8954 in row_mysql_handle_errors (new_err=0x7f8422a6660c, trx=0x7f83648ca478, thr=0x7f836495e550, savept=0x7f8422a66610) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/row/row0mysql.cc:688
#7 0x0000000000bd9dd7 in row_insert_for_mysql (mysql_rec=0x7f836489b010 <incomplete sequence \375>, prebuilt=0x7f836495de78) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/row/row0mysql.cc:1379
#8 0x0000000000ad6a65 in ha_innobase::write_row (this=0x7f83648aa510, record=0x7f836489b010 <incomplete sequence \375>) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/handler/ha_innodb.cc:7296
#9 0x000000000064c9ed in handler::ha_write_row (this=0x7f83648aa510, buf=0x7f836489b010 <incomplete sequence \375>) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/handler.cc:7648
#10 0x00000000007c4155 in write_record (thd=0x7f838dbf2000, table=0x7f8364851600, info=0x7f8422a66970, update=0x7f8422a669f0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_insert.cc:1947
#11 0x00000000007c1f68 in mysql_insert (thd=0x7f838dbf2000, table_list=0x7f836481f1b8, fields=..., values_list=..., update_fields=..., update_values=..., duplic=DUP_ERROR, ignore=false) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_insert.cc:1085
#12 0x00000000007e5262 in mysql_execute_command (thd=0x7f838dbf2000) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:3851
#13 0x00000000007ed193 in mysql_parse (thd=0x7f838dbf2000, rawbuf=0x7f836481f010 "INSERT INTO t1 VALUES('����'),('����'),('����'),('����'),('����'),('����')", length=122, parser_state=0x7f8422a67df0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:6773
#14 0x00000000007df5fc in dispatch_command (command=COM_QUERY, thd=0x7f838dbf2000, packet=0x7f8384641001 "INSERT INTO t1 VALUES('����'),('����'),('����'),('����'),('����'),('����')", packet_length=122) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:1432
#15 0x00000000007de528 in do_command (thd=0x7f838dbf2000) at /mnt/workspace/percona-server-5.6-binaries-de...

Read more...

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

innodb_limit_optimistic_insert_debug=1 renders the testcase not relevant for us

Revision history for this message
sbester (sbester) wrote :
tags: removed: qablock
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.