[MCOL-3692] INSERT .. SELECT executed after previous interrupted operation causes ER_INTERNAL_ERROR Created: 2019-12-25  Updated: 2019-12-26  Resolved: 2019-12-26

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: 1.4.2
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

drop table if exists t1;
create table t1 (a int) engine=Columnstore;
set statement max_statement_time=1 for insert into t1 select seq from seq_1_to_10000000;
insert into t1 select seq from seq_1_to_2;

MariaDB f93bfb9288d020b190f5c73a31223fff6439687d

MariaDB [db]> create table t1 (a int) engine=Columnstore;
Query OK, 0 rows affected (0.632 sec)
 
MariaDB [db]> set statement max_statement_time=1 for insert into t1 select seq from seq_1_to_10000000;
ERROR 1969 (70100): Query execution was interrupted (max_statement_time exceeded)
MariaDB [db]> insert into t1 select seq from seq_1_to_2;
ERROR 1815 (HY000): Internal error: PM1 : Bulkload Read (thread 0) Failed for Table db.t1.  Terminating this job.

Time interval between the interrupted operation and the next one does not matter, even half an hour later it still returns the error.
Next identical INSERT works fine.



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-12-26 ]

Technically could sort-of be classed as a bug due to the error message. But this isn't fixable until we replace the bulk insert code (intended for 1.5).

The reason is the first abort leaves a table lock behind which needs to be manually cleared.

Generated at Thu Feb 08 02:44:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.