Deploy Single-Node Enterprise ColumnStore with Local Storage
Contents
Overview
This procedure describes the deployment of the Single-Node Enterprise ColumnStore topology with Local storage.
MariaDB Enterprise ColumnStore 23.10 is a columnar storage engine for MariaDB Enterprise Server and 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.
Procedure Steps
| Step | Description |
|---|---|
| Step 1 | Prepare System for Enterprise ColumnStore |
| Step 2 | Install Enterprise ColumnStore |
| Step 3 | Start and Configure Enterprise ColumnStore |
| Step 4 | Test Enterprise ColumnStore |
| Step 5 | Bulk Import Data to Enterprise ColumnStore |
Support
Customers can obtain support by submitting a support case.
Components
The following components are deployed during this procedure:
| Component | Function |
|---|---|
| MariaDB Enterprise Server 10.5 | Modern SQL RDBMS with high availability, pluggable storage engines, hot online backups, and audit logging. |
MariaDB Enterprise Server Components
| Component | Description |
|---|---|
| MariaDB Enterprise ColumnStore | • Columnar Storage Engine • Optimized for Online Analytical Processing (OLAP) workloads |
Topology
The Single-Node Enterprise ColumnStore topology provides support for Online Analytical Processing (OLAP) workloads to MariaDB Enterprise Server.
The Enterprise ColumnStore node:
Receives queries from the application
Executes queries
Uses the local disk for storage.
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 Shared Local storage.
Requirements
These requirements are for the Single-Node Enterprise ColumnStore, when deployed with MariaDB Enterprise Server and MariaDB Enterprise ColumnStore 23.10.
Operating System
- Debian 11 (x86_64, ARM64)
- Debian 12 (x86_64, ARM64)
- Red Hat Enterprise Linux 8 (x86_64, ARM64)
- Red Hat Enterprise Linux 9 (x86_64, PPC64LE, ARM64)
- Red Hat UBI 8 (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)
- Ubuntu 24.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:
| Component | CPU | Memory |
|---|---|---|
| MaxScale 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.
Recommended Hardware Requirements
MariaDB Enterprise ColumnStore's recommended hardware requirements are intended for production analytics.
The recommended hardware requirements are:
| Component | CPU | Memory |
|---|---|---|
| Enterprise ColumnStore node | 64+ cores | 128+ GB |
Quick Reference
MariaDB Enterprise Server Configuration Management
| Method | Description |
|---|---|
| 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. |
| Command-line | The server can be started with command-line options that set system-variables and options. |
| SQL | 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.
| Distribution | Example Configuration File Path |
|---|---|
| • CentOS • Red Hat Enterprise Linux (RHEL) | /etc/my.cnf.d/z-custom-mariadb.cnf |
| • Debian • Ubuntu | /etc/mysql/mariadb.conf.d/z-custom-mariadb.cnf |
MariaDB Enterprise Server Service Management
The systemctl command is used to start and stop the MariaDB Enterprise Server service. The galera_new_cluster and galera_recovery scripts are used for Enterprise Cluster-specific operations.
| Operation | Command |
|---|---|
| Start | sudo systemctl start mariadb |
| Stop | sudo systemctl stop mariadb |
| Restart | sudo systemctl restart mariadb |
| Enable during startup | sudo systemctl enable mariadb |
| Disable during startup | sudo systemctl disable mariadb |
| Status | sudo systemctl status mariadb |
| Bootstrap a cluster node | sudo galera_new_cluster |
| Recover a cluster node's position | sudo galera_recovery |
Next Step
Navigation in the Single-Node Enterprise ColumnStore topology with Local storage deployment procedure:
