[MCOL-2049] Having issues loading data into ColumnStore Created: 2018-12-25  Updated: 2021-01-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: cpimport
Affects Version/s: 1.2.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Justin Swanhart (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Debian 9



 Description   

Trying to load data, and I'm getting errors about ExeMgr:
mysql> use ssb;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> \. /tmp/load.sql
yuERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
ERROR 1815 (HY000): Internal error: IDB-2004: Cannot connect to ExeMgr.
^Z
[1]+ Stopped mysql -h127.0.0.1 -P3306
root@debian-c-32-64gib-nyc1-01:~/swanhart-tools/shard-query/bin# bg
[1]+ mysql -h127.0.0.1 -P3306 &
root@debian-c-32-64gib-nyc1-01:~/swanhart-tools/shard-query/bin# terror
Dec 25 22:26:54 debian-c-32-64gib-nyc1-01 controllernode[5161]: 54.284066 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getTxnID() failed (network)
Dec 25 22:27:44 debian-c-32-64gib-nyc1-01 joblist[5161]: 44.424520 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:27:49 debian-c-32-64gib-nyc1-01 joblist[5161]: 49.438374 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:27:49 debian-c-32-64gib-nyc1-01 controllernode[5161]: 49.453035 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getTxnID() failed (network)
Dec 25 22:28:39 debian-c-32-64gib-nyc1-01 joblist[5161]: 39.593340 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:28:44 debian-c-32-64gib-nyc1-01 joblist[5161]: 44.608105 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:28:44 debian-c-32-64gib-nyc1-01 controllernode[5161]: 44.623095 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getTxnID() failed (network)
Dec 25 22:29:34 debian-c-32-64gib-nyc1-01 joblist[5161]: 34.761710 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:29:39 debian-c-32-64gib-nyc1-01 joblist[5161]: 39.762232 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/debian9/mariadb-columnstore-engine/dbcon/execplan/clientrotator.cpp @ 369 Could not get a ExeMgr connection.
Dec 25 22:29:39 debian-c-32-64gib-nyc1-01 controllernode[5161]: 39.776533 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getTxnID() failed (network)

table DDL:
CREATE TABLE IF NOT EXISTS lineorder
(
LO_OrderKey bigint not null,
LO_LineNumber tinyint not null,
LO_CustKey int not null,
LO_PartKey int not null,
LO_SuppKey int not null,
LO_OrderDateKey int not null,
LO_OrderPriority varchar(15),
LO_ShipPriority char(1),
LO_Quantity tinyint,
LO_ExtendedPrice decimal,
LO_OrdTotalPrice decimal,
LO_Discount decimal,
LO_Revenue decimal,
LO_SupplyCost decimal,
LO_Tax tinyint,
LO_CommitDateKey int not null,
LO_ShipMode varchar(10)
);

LOAD DATA INFILE '/tmp/lineorder.tbl.1' INTO TABLE lineorder FIELDS TERMINATED BY '|';

generate the data with http://github.com/greenlion/ssb-dbgen
./dbgen -T l -s 160 -C 32 (where 32 is number of cores)



 Comments   
Comment by David Hill (Inactive) [ 2018-12-26 ]

Is the ExeMgr running?

Can find out with these commands:

  1. mcsadmin getsystemi
  2. ps -ef | grep ExeMgr

Can run these to get ExeMgr or system running

  1. mcsadmin shutdown y
  2. mcsadmin startsystem
Comment by Andrew Hutchings (Inactive) [ 2019-12-04 ]

Likely ExeMgr failed for some reason, if so there are likely crash dumps to explain why. Using columnstoreSupport would help us diagnose this.

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