Comments - Writing and Editing Knowledge Base Articles
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
if we do an create table with engine=columnstore the command hangs, and the table is not created.
At mcsadmin we see INITAL at DMLProc ->
MariaDB ColumnStore Process statuses
Process Module Status Last Status Change Process ID ------------------ ------ --------------- ------------------------ ---------- ProcessMonitor pm1 ACTIVE Mon Mar 18 13:12:42 2019 80615 ProcessManager pm1 ACTIVE Mon Mar 18 13:12:49 2019 80810 DBRMControllerNode pm1 ACTIVE Tue Mar 19 11:54:45 2019 45740 ServerMonitor pm1 ACTIVE Tue Mar 19 11:54:48 2019 45799 DBRMWorkerNode pm1 ACTIVE Tue Mar 19 11:54:47 2019 45823 PrimProc pm1 ACTIVE Tue Mar 19 11:55:14 2019 46592 ExeMgr pm1 ACTIVE Tue Mar 19 11:55:28 2019 46882 WriteEngineServer pm1 ACTIVE Tue Mar 19 11:54:59 2019 46181 DDLProc pm1 ACTIVE Tue Mar 19 11:55:03 2019 46347 DMLProc pm1 INITIAL Tue Mar 19 11:55:08 2019 46446 mysqld pm1 ACTIVE Tue Mar 19 11:54:44 2019 45623
And this can NOT be cleared by stop & startSystem!
We use mariadb-columnstore-1.2.2-1-sles12.x86_64
on an single system. Therefore we use /usr/local/mariadb/columnstore/bin/quick_installer_single_server.sh for setup.
Any idea why the create table hangs up?