[MCOL-14] concurDDL test in autopilot failed Created: 2016-05-03  Updated: 2016-08-16  Resolved: 2016-08-16

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

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

Issue Links:
Relates
relates to MCOL-35 211 Concurrent Transactions Test failed Closed
Sprint: 1.0.2-2

 Description   

One script runs by it self works. Multiple scripts running concurrently does not. out of 25 tables in 5 scripts, only 5 were created in the front end and only 1 created in the backend.

 Comments   
Comment by Daniel Lee (Inactive) [ 2016-05-26 ]

This issue can be reproduced with Autopilot test concurrency.concurDDL. Additional tests runs suggested that system catalog may not be in a good state after this issue has occurred, and MCOL-64 and MCOL-66 failed as a result of this.

This is the errors outputted by concurDDL test:

[10:35]
ERROR 1815 (HY000) at line 1: Internal error: CAL0009: Create table failed due to boost: mutex lock failed in pthread_mutex_lo
ck: Invalid argument
ERROR 1815 (HY000) at line 53: Internal error: CAL0009: Create table failed due to WE: Error updating calpontsys.systable: a B
RM Begin copy error.
ERROR 1815 (HY000) at line 105: Internal error: CAL0009: Create table failed due to WE: Error updating calpontsys.systable: a
BRM Begin copy error.
ERROR 2013 (HY000) at line 157: Lost connection to MySQL server during query
ERROR 2006 (HY000) at line 209: MySQL server has gone away

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

Repeated test and it worked successfully.

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