[MDEV-13191] Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' fails on LOAD DATA, main.mysqldump fails in buildbot and outside Created: 2017-06-27  Updated: 2017-07-02  Resolved: 2017-07-02

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients, Tests
Affects Version/s: 10.2
Fix Version/s: 10.1.26, 10.0.32, 10.2.7

Type: Bug Priority: Blocker
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: regression


 Description   

10.2 29624ea304b5893d3bc81670807285a89fce1a33

$ perl ./mtr main.mysqldump --repeat=10 
 
mysqld: /data/src/10.2/sql/sql_error.cc:380: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed.
170627 15:16:30 [ERROR] mysqld got signal 6 ;
 
#7  0x00007f358a0cbee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00005570db7be44f in Diagnostics_area::set_ok_status (this=0x7f351c005b10, affected_rows=50, last_insert_id=0, message=0x7f357c462140 "Records: 50  Deleted: 0  Skipped: 0  Warnings: 1") at /data/src/10.2/sql/sql_error.cc:380
#9  0x00005570db771921 in my_ok (thd=0x7f351c000b00, affected_rows=50, id=0, message=0x7f357c462140 "Records: 50  Deleted: 0  Skipped: 0  Warnings: 1") at /data/src/10.2/sql/sql_class.h:4324
#10 0x00005570dbbfb09b in mysql_load (thd=0x7f351c000b00, ex=0x7f351c011188, table_list=0x7f351c011228, fields_vars=..., set_fields=..., set_values=..., handle_duplicates=DUP_ERROR, ignore=false, read_file_from_client=false) at /data/src/10.2/sql/sql_load.cc:743
#11 0x00005570db7eea66 in mysql_execute_command (thd=0x7f351c000b00) at /data/src/10.2/sql/sql_parse.cc:4810
#12 0x00005570db7f8432 in mysql_parse (thd=0x7f351c000b00, rawbuf=0x7f351c011008 "LOAD DATA   INFILE '/data/bld/10.2/mysql-test/var/std_data/words2.dat' INTO TABLE `words2` IGNORE 0 LINES", length=105, parser_state=0x7f357c463200, is_com_multi=false, is_next_command=false) at /data/src/10.2/sql/sql_parse.cc:7879
#13 0x00005570db7e64df in dispatch_command (command=COM_QUERY, thd=0x7f351c000b00, packet=0x7f351c149ab1 "", packet_length=105, is_com_multi=false, is_next_command=false) at /data/src/10.2/sql/sql_parse.cc:1817
#14 0x00005570db7e4e20 in do_command (thd=0x7f351c000b00) at /data/src/10.2/sql/sql_parse.cc:1362
#15 0x00005570db9304d9 in do_handle_one_connection (connect=0x5570df99d3d0) at /data/src/10.2/sql/sql_connect.cc:1354
#16 0x00005570db930266 in handle_one_connection (arg=0x5570df99d3d0) at /data/src/10.2/sql/sql_connect.cc:1260
#17 0x00005570dbd4ae6a in pfs_spawn_thread (arg=0x5570df363840) at /data/src/10.2/storage/perfschema/pfs.cc:1862
#18 0x00007f358c010494 in start_thread (arg=0x7f357c464700) at pthread_create.c:333
#19 0x00007f358a18893f in clone () from /lib/x86_64-linux-gnu/libc.so.6

The problem appeared in 10.2 tree after a recent libmariadb submodule upgrade, apparently with this revision:

commit 1ea7be32f5e95c2728bd8395b6c7e7d1c582cc6b
Merge: 06d2490 e50571e
Author: Georg Richter <georg@mariadb.com>
Date:   Wed Jun 14 11:12:59 2017 +0200
 
    Merge remote-tracking branch 'origin/MDEV-12471'



 Comments   
Comment by Michael Widenius [ 2017-07-02 ]

This could happen when the client connection dies while sending a progress report packet.
Fixed by not raising any errors when sending progress packets.

Comment by Michael Widenius [ 2017-07-02 ]

Pushed into 10.0 tree, as this issue can happen here too.

Generated at Thu Feb 08 08:03:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.