[MCOL-277] Concurrent Online Table name change and Select Error Created: 2016-08-29  Updated: 2018-12-20  Resolved: 2018-12-20

Status: Closed
Project: MariaDB ColumnStore
Component/s: DDLProc
Affects Version/s: None
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Dipti Joshi (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

This error is reported by a InfiniDB user. It should be checked in MariaDB ColumnStore as well.

"We noticed error occurs when there are two processes attempting to access an infinidb table at the same time:
Process 1:

  • RENAME TABLE tbl_old to tbl_new;
    Process 2:
  • SELECT * FROM (tbl_old UNION tbl_1 UNION tbl_2)

This is the error
DBD::mysql::st execute failed: An unexpected condition within the query caused an internal processing error within InfiniDB. Please check the log files for more details. Additional Information: error in BatchPrimitiveProcessor projectResult. Please check crit.log for more details.

The crit.log is empty.
"

 Comments   
Comment by Daniel Lee (Inactive) [ 2016-08-29 ]

I performed the following tests and could not reproduce the report issue:

ColumnStore 1.0.2.1-1 on single server
InfiniDB 4.6.1-1 on single server
ColumnStore 1.0.2-1 on 1 UM, 1 PM

I did many test runs, varying the time since the query started, to rename the table. That tested different scenarios that the table was renamed at different stages of the query processing (data retrieval, outputting rows to terminal, etc).

SQL statements used for testing:

select * from (select * from orders union select * from orders1 union select * from orders2) a;
rename table orders to orders5;

Table size used was TPCH 1g ( 500000 rows for each table)

We should contact the customer to get the exact test scenario, as well as the table size, just in case what I tested is different from their scenario.

Comment by Dipti Joshi (Inactive) [ 2016-08-30 ]

Please do it on a table with 93 million rows

Comment by David Tse [ 2017-03-06 ]

I also encounter this issue randomly. Anyone has found a workaround?

Shortly after renaming a table with about 6.5 million rows. Select on this table will have below errors

MySQL Error: 1815 - Internal error: An unexpected
condition within the query caused an internal
processing error within InfiniDB. Please check the
log files for more details. Additional
Information: error in BatchPrimitiveProces

Comment by Daniel Lee (Inactive) [ 2017-06-08 ]

Unable to reproduced the issue on both ColumnStore 1.1.0 and InfiniDB 4.6.7-1.

The test was to have 5 concurrent sessions, each to rename the lineitem table to lineitem1 and back, and select from the it. As expected, the tests resulted some "table does not exist" errors, but not the issues that were described in the ticket.

Comment by Andrew Hutchings (Inactive) [ 2018-12-20 ]

Couldn't reproduce the problem

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