[MCOL-5552] /usr/bin/mariadb-columnstore-start.sh Doesn't Start Columnstore Created: 2023-08-10  Updated: 2023-08-25

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

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

Kubernetes Pod, docker.io/amd64/ubuntu:focal

Attachments: PNG File Screenshot 2023-08-10 at 2.41.29 PM.png    

 Description   

Per the title, the start script returns an error using a Ubuntu image. I cannot use your docker image in our compliance-heavy environment.

I'm following these very sparse instructions. https://mariadb.com/docs/server/deploy/topologies/single-node/community-columnstore-cs10-6/

exec

{fd_lock}>/var/lib/columnstore/storagemanager/storagemanager-lock
flock -n "$fd_lock" || exit 0

Error message: /usr/bin/mariadb-columnstore-start.sh: 7: exec: {fd_lock}

: not found

My understanding is flock takes 2 arguments? I'm not an expert though.

Another bug: The systemd configs do not start a worker node in Kubernetes.

Another bug: neither the rsyslog nor syslog-ng configs generate the intended log files.

Another bug: the syslog-ng config that ships prevents syslog-ng from starting.

Not a bug, but, using systemd seems like not the wisest choice in an industry obsessed with Kubernetes/microservices.

Finally, is there a reason the components of this project are completely undocumented and without verbose options? Trying to compete with Oracle and Microsoft on secret-keeping doesn't make Mariadb the better choice between secret-keepers Microsoft and Oracle.
Generated at Thu Feb 08 02:58:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.