[MCOL-5551] Deploying on Kubernetes and Ubuntu Does Not Work Created: 2023-08-09  Updated: 2023-08-25

Status: Open
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 23.02.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Ricky Bobby Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Columnstore, columnstoreSupport
Environment:

Linux Ubuntu image: docker.io/amd64/ubuntu:focal


Attachments: PNG File Screenshot 2023-08-09 at 4.19.26 PM.png     PNG File Screenshot 2023-08-09 at 4.22.02 PM.png     PNG File Screenshot 2023-08-09 at 4.24.10 PM.png     PNG File Screenshot 2023-08-09 at 4.26.31 PM.png     PNG File Screenshot 2023-08-09 at 4.28.12 PM.png     PNG File Screenshot 2023-08-09 at 4.53.20 PM.png    

 Description   

Another ridiculously long bug report. The attempt is to deploy just one pod that actually works. Nothing as fancy as the undocumented cluster config.

First: I can't pull your docker repo image. It's a heavily regulated environment. That means I use a compliant image currently based on image: docker.io/amd64/ubuntu:focal

Second: This is a proof of concept. If there's any possibility of spending money at MariaDB, the proof of concept has to work.

I have so many more questions, but basically the scant documentation to run columnstore in even a single pod isn't correct for 11.1.

Scant documentation: https://mariadb.com/docs/server/deploy/topologies/single-node/community-columnstore-cs10-6/

Getting the repo configured, and packages installed works... Sort of.

/etc/rsyslog.d/49-columnstore.conf is created. But, doesn't seem to do anything? Everything is logged to /var/log/syslog.

I couldn't create a table. Is there logging somewhere else? Reboots destroy everything despite using persistent volumes??

tail /var/log/syslog
Aug 9 23:07:03 mariadb11-0 DMLProc[9667]: 03.349525 |0|0|0| I 20 CAL0002: DMLProc finished rollbackAll.
Aug 9 23:07:03 mariadb11-0 ddlpackageproc[9664]: 03.354914 |0|0|0| C 23 CAL0008: DMLProc main process has started
Aug 9 23:07:07 mariadb11-0 ddlpackageproc[9684]: 07.595832 |0|0|0| C 23 CAL0008: DDLProc main process has started
Aug 9 23:16:26 mariadb11-0 workernode[9831]: 26.473212 |0|0|0| C 30 CAL0000: Usage: /usr/bin/workernode DBRM_WorkerN %%10%%
Aug 9 23:16:35 mariadb11-0 workernode[9835]: 35.761498 |0|0|0| I 30 CAL0000: WorkerNode main process has started %%10%%
Aug 9 23:25:24 mariadb11-0 workernode[9955]: 24.346956 |0|0|0| C 30 CAL0000: Usage: workernode DBRM_WorkerN %%10%%
Aug 9 23:52:52 mariadb11-0 ddlpackageproc[9686]: 52.292228 |19|6|0| D 23 CAL0041: Start SQL statement: create table foo (`interactionId` varchar(64) NOT NULL,#012 `number` int(11) unsigned DEFAULT NULL,#012 `accountId` varchar(64) DEFAULT NULL,#012 `queueId` varchar(64) DEFAULT NULL) ENGINE=columnStore DEFAULT CHARSET=latin1;|db1|
Aug 9 23:52:52 mariadb11-0 controllernode[9686]: 52.294864 |0|0|0| W 29 CAL0000: ExtentMap::getSysCatDBRoot(): OID not found: 1001 %%10%%
Aug 9 23:52:52 mariadb11-0 ddlpackageproc[9686]: 52.295288 |19|6|0| D 23 CAL0042: End SQL statement
Aug 9 23:52:52 mariadb11-0 ddlpackageproc[9686]: 52.296787 |0|0|0| E 23 CAL0009: Error while calling getSysCatDBRoot


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