Deploy Single-Node Enterprise ColumnStore 5 with Local Storage
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Deploy Single-Node Topologies
Topics on this page:
This procedure describes the deployment of the Single-Node Enterprise ColumnStore topology with Local storage.
MariaDB Enterprise ColumnStore 5 is a columnar storage engine for MariaDB Enterprise Server 10.5. 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:
Modern SQL RDBMS with high availability, pluggable storage engines, hot online backups, and audit logging.
MariaDB Enterprise Server Components
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
Uses the local disk for storage.
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 5 with Shared Local storage.
These requirements are for the Single-Node Enterprise ColumnStore, when deployed with MariaDB Enterprise Server 10.5 and MariaDB Enterprise ColumnStore 5.
CentOS Linux 7 (x86_
Debian 10 (x86_
Red Hat Enterprise Linux 7 (x86_
Red Hat Enterprise Linux 8 (x86_
Ubuntu 18.04 LTS (x86_
Ubuntu 20.04 LTS (x86_
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
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
Apr 30 21:54:35 a1ebc96a2519 PrimProc: 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:
Enterprise ColumnStore node
MariaDB Enterprise Server Configuration Management
Configuration files (such as
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
MariaDB Enterprise Server Service Management
systemctl command is used to start and stop the MariaDB Enterprise Server service.
Enable during startup
Disable during startup
Navigation in the Single-Node Enterprise ColumnStore topology with Local storage deployment procedure: