[MCOL-4315] mariadb 10.5 with Columnstore stuck during queries, do no kill queries and cannot be shut down Created: 2020-09-18  Updated: 2021-04-19  Resolved: 2021-01-15

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

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

single node Centos 7.8



 Description   

Reported by customer:

this morning we found a lot of queries that normally take aprox 1 second, waiting for more than 6000 seconds.
We tried to kill the queries from mariadb shell, but after 5 minutes they all where yet there, despite the status was "killed".
Also tried to cleanly shutdown mariadb process (systemctl stop mariadb) but after several minutes the process was yet alive.
We had to kill mariadbd with kill -9
The queries running where all involving Columnstore tables.
We are using columnstore_select_handler=0 as GLOBAL because we need to do INSERT....SELECT and several kind of
joins that select_handler still not support (after years, that's incredibile), but we don't know if this setting is causing this issue or any other in terms of performances.
The server is a single node with both InnoDB and Columnstore.

In case report:

  • snapshot of sqlyog showing query stalled
  • snapshot of sqlyog showing query killed but still there
  • output of "/usr/bin/columnstoreSupport -a";
  • mariadb error.log (sw-mcs.err)
  • output of "SHOW STATUS"


 Comments   
Comment by Todd Stoffel (Inactive) [ 2021-01-15 ]

"select handler" must be ON or it will go into a very slow row by row process.

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