Deploy Single-Node Enterprise ColumnStore 23.10 with Object Storage


This procedure describes the deployment of the Single-Node Enterprise ColumnStore topology with Object storage.

MariaDB Enterprise ColumnStore 23.10 is a columnar storage engine for MariaDB Enterprise Server 23.07. Enterprise ColumnStore is best suited for Online Analytical Processing (OLAP) workloads.

This procedure has 5 steps, which are executed in sequence.

This page provides an overview of the topology, requirements, and deployment procedures.

Please read and understand this procedure before executing.


Customers can obtain support by submitting a support case.


The following components are deployed during this procedure:



MariaDB Enterprise Server 23.07

Modern SQL RDBMS with high availability, pluggable storage engines, hot online backups, and audit logging.

MariaDB Enterprise Server Components



MariaDB Enterprise ColumnStore 23.10

  • Columnar Storage Engine

  • Optimized for Online Analytical Processing (OLAP) workloads

  • S3-compatible object storage


Single-Node Enterprise ColumnStore Topology with Object Storage

The Single-Node Enterprise ColumnStore topology provides support for Online Analytical Processing (OLAP) workloads to MariaDB Enterprise Server.

The Enterprise ColumnStore node:

High Availability

Single-Node Enterprise ColumnStore does not provide high availability (HA) for Online Analytical Processing (OLAP). If you would like to deploy Enterprise ColumnStore with high availability, see Enterprise ColumnStore 23.10 with Object storage.


These requirements are for the Single-Node Enterprise ColumnStore, when deployed with MariaDB Enterprise Server 23.07 and MariaDB Enterprise ColumnStore 23.10.

Operating System

  • CentOS Linux 7 (x86_64)

  • Debian 11 (x86_64, ARM64)

  • Debian 12 (x86_64, ARM64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Red Hat Enterprise Linux 9 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • Rocky Linux 9 (x86_64, ARM64)

  • Ubuntu 20.04 LTS (x86_64, ARM64)

  • Ubuntu 22.04 LTS (x86_64, ARM64)

Minimum Hardware Requirements

MariaDB Enterprise ColumnStore's minimum hardware requirements are not intended for production environments, but the minimum hardware requirements can be appropriate for development and test environments. For production environments, see the recommended hardware requirements instead.

The minimum hardware requirements are:




Enterprise ColumnStore node

4+ cores

16+ GB

MariaDB Enterprise ColumnStore will refuse to start if the system has less than 3 GB of memory.

If Enterprise ColumnStore is started on a system with less memory, the following error message will be written to the ColumnStore system log called crit.log:

Apr 30 21:54:35 a1ebc96a2519 PrimProc[1004]: 35.668435 |0|0|0| C 28 CAL0000: Error total memory available is less than 3GB.

And the following error message will be raised to the client:

ERROR 1815 (HY000): Internal error: System is not ready yet. Please try again.

Storage Requirements

Single-node Enterprise ColumnStore with Object Storage requires the following storage type:

Storage Type


S3-Compatible Object Storage

Single-node Enterprise ColumnStore with Object Storage uses S3-compatible object storage to store data.

S3-Compatible Object Storage Requirements

Single-node Enterprise ColumnStore with Object Storage uses S3-compatible object storage to store data.

Many S3-compatible object storage services exist. MariaDB Corporation cannot make guarantees about all S3-compatible object storage services, because different services provide different functionality.

For the preferred S3-compatible object storage providers that provide cloud and hardware solutions, see the following sections:

The use of non-cloud and non-hardware providers is at your own risk.

If you have any questions about using specific S3-compatible object storage with MariaDB Enterprise ColumnStore, contact us.

Preferred Object Storage Providers: Cloud

  • Amazon Web Services (AWS) S3

  • Google Cloud Storage

  • Azure Storage

  • Alibaba Cloud Object Storage Service

Preferred Object Storage Providers: Hardware

  • Cloudian HyperStore

  • Dell EMC

  • Seagate Lyve Rack

  • Quantum ActiveScale

  • IBM Cloud Object Storage

Quick Reference

MariaDB Enterprise Server Configuration Management



Configuration File

Configuration files (such as /etc/my.cnf) can be used to set system-variables and options. The server must be restarted to apply changes made to configuration files.


The server can be started with command-line options that set system-variables and options.


Users can set system-variables that support dynamic changes on-the-fly using the SET statement.

MariaDB Enterprise Server packages are configured to read configuration files from different paths, depending on the operating system. Making custom changes to Enterprise Server default configuration files is not recommended because custom changes may be overwritten by other default configuration files that are loaded later.

To ensure that your custom changes will be read last, create a custom configuration file with the z- prefix in one of the include directories.


Example Configuration File Path

  • CentOS

  • Red Hat Enterprise Linux (RHEL)


  • Debian

  • Ubuntu


MariaDB Enterprise Server Service Management

The systemctl command is used to start and stop the MariaDB Enterprise Server service.




sudo systemctl start mariadb


sudo systemctl stop mariadb


sudo systemctl restart mariadb

Enable during startup

sudo systemctl enable mariadb

Disable during startup

sudo systemctl disable mariadb


sudo systemctl status mariadb