What's New in MariaDB Enterprise ColumnStore 5?

MariaDB Enterprise ColumnStore 5 is included with MariaDB Enterprise Server 10.5.

The new features in MariaDB Enterprise ColumnStore 5 are listed below.

MariaDB Enterprise Server Convergence

MariaDB has been continually improving the integration of MariaDB Enterprise ColumnStore with MariaDB Enterprise Server:

MariaDB Enterprise ColumnStore 5 simplifies the installation procedure. Installing the ColumnStore storage engine is similar to installing other storage engines for MariaDB Enterprise Server.

Available Versions

The version of MariaDB Enterprise ColumnStore 5 depends on the version of MariaDB Enterprise Server being used:

ES Version

Enterprise ColumnStore Version

ES 10.5.9-6

MariaDB Enterprise ColumnStore 5.5.2

ES 10.5.8-5

MariaDB Enterprise ColumnStore 5.5.1

ES 10.5.6-4

Installation

MariaDB Enterprise ColumnStore 5 simplifies the installation procedure. Installing the ColumnStore storage engine is similar to installing other storage engines for MariaDB Enterprise Server.

For single-node and multi-node Enterprise ColumnStore 5 deployments, the ColumnStore storage engine, the ColumnStore command-line interfaces, and other internal ColumnStore components are deployed by installing a single package in addition to the MariaDB Enterprise Server package.

For multi-node Enterprise ColumnStore 5 deployments, the Cluster Management API (CMAPI) server must be deployed by installing another package.

Installing Enterprise ColumnStore 5 no longer requires running columnstore-post-install or postConfigure.

Enterprise ColumnStore 5 can be installed to run as a non-root user.

Note

To install this version, see "Deploy".

Clients

MariaDB Enterprise ColumnStore 5 adds support for Microsoft Power BI Direct Query Adapter.

Administration

MariaDB Enterprise ColumnStore 5 simplifies administration.

Enterprise ColumnStore 5 no longer includes or supports mcsadmin.

For single-node and multi-node Enterprise ColumnStore 5 deployments, the Enterprise ColumnStore 5 service is administered by systemd:

Operation

Command

Start

sudo systemctl start mariadb-columnstore

Stop

sudo systemctl stop mariadb-columnstore

Restart

sudo systemctl restart mariadb-columnstore

Enable during startup

sudo systemctl enable mariadb-columnstore

Disable during startup

sudo systemctl disable mariadb-columnstore

Status

sudo systemctl status mariadb-columnstore

For multi-node Enterprise ColumnStore 5 deployments, systemd is not used to stop and start the Enterprise ColumnStore 5 services. Cluster Management API (CMAPI) server runs on every node and ensures that the Enterprise ColumnStore 5 services are running. CMAPI server provides a REST API that can be used to perform administrative operations:

Endpoint Path

Method

Action

add-node

PUT

Adds a ColumnStore node

mode-set

PUT

Sets all ColumnStore nodes to read-only or read-write

remove-node

PUT

Removes a ColumnStore node

shutdown

PUT

Shuts down ColumnStore on all nodes

start

PUT

Starts ColumnStore on all nodes

status

GET

Checks the status of ColumnStore

The Cluster Management API (CMAPI) service is administered by systemd:

Operation

Command

Start

sudo systemctl start mariadb-columnstore-cmapi

Stop

sudo systemctl stop mariadb-columnstore-cmapi

Restart

sudo systemctl restart mariadb-columnstore-cmapi

Enable during startup

sudo systemctl enable mariadb-columnstore-cmapi

Disable during startup

sudo systemctl disable mariadb-columnstore-cmapi

Status

sudo systemctl status mariadb-columnstore-cmapi

Multi-Node

MariaDB Enterprise ColumnStore 5 supports multi-node deployments for high availability and load balancing. Multi-node Enterprise ColumnStore 5 requires an odd number of ColumnStore nodes with a minimum of 3.

Multi-node Enterprise ColumnStore 5 requires MariaDB MaxScale 2.5 for high availability and load balancing. Multi-node Enterprise ColumnStore requires at least one MaxScale node. For highly available load balancing, multiple MaxScale nodes can be used by configuring cooperative locking.

Multi-node Enterprise ColumnStore 5 requires CMAPI server to be running on every ColumnStore node. CMAPI server provides a REST API that can be used to perform administrative operations

S3-Compatible Object Storage

MariaDB Enterprise ColumnStore supports S3-compatible object storage.

S3-compatible object storage is optional, but highly recommended. If S3-compatible object storage is used, Enterprise ColumnStore requires the Storage Manager directory to use shared local storage (such as NFS) for high availability.

S3-compatible object storage is:

  • Compatible: Many object storage services are compatible with the Amazon S3 API.

  • Economical: S3-compatible object storage is often very low cost.

  • Flexible: S3-compatible object storage is available for both cloud and on-premises deployments.

  • Limitless: S3-compatible object storage is often virtually limitless.

  • Resilient: S3-compatible object storage is often low maintenance and highly available, since many services use resilient cloud infrastructure.

  • Scalable: S3-compatible object storage is often highly optimized for read and write scaling.

  • Secure: S3-compatible object storage is often encrypted-at-rest.

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.

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

Enterprise ColumnStore 5 supports IAM roles with S3-compatible object storage.

Shared Local Storage

MariaDB Enterprise ColumnStore can use shared local storage.

Shared local storage is required for high availability. The specific shared local storage requirements depend on whether Enterprise ColumnStore is configured to use S3-compatible object storage:

  • When S3-compatible object storage is used, Enterprise ColumnStore requires the Storage Manager directory to use shared local storage for high availability.

  • When S3-compatible object storage is not used, Enterprise ColumnStore requires the DB Root directories to use shared local storage for high availability.

The most common shared local storage options for on-premises and cloud deployments are:

  • NFS (Network File System)

  • GlusterFS

The most common shared local storage options for AWS (Amazon Web Services) deployments are:

  • EBS (Elastic Block Store) Multi-Attach

  • EFS (Elastic File System)

The most common shared local storage option for GCP (Google Cloud Platform) deployments is:

  • Filestore

Shared Local Storage Options

The most common options for shared local storage are:

Shared Local Storage

Description

EBS (Elastic Block Store) Multi-Attach

  • EBS is a high-performance block-storage service for AWS (Amazon Web Services).

  • EBS Multi-Attach allows an EBS volume to be attached to multiple instances in AWS. Only clustered file systems, such as GFS2, are supported.

  • For deployments in AWS, EBS Multi-Attach is a recommended option for the Storage Manager directory, and Amazon S3 storage is the recommended option for data.

EFS (Elastic File System)

  • EFS is a scalable, elastic, cloud-native NFS file system for AWS (Amazon Web Services).

  • For deployments in AWS, EFS is a recommended option for the Storage Manager directory, and Amazon S3 storage is the recommended option for data.

Filestore

NFS (Network File System)

  • NFS is a distributed file system.

  • If NFS is used, the storage should be mounted with the sync option to ensure that each node flushes its changes immediately.

  • For on-premises deployments, NFS is the recommended option for the Storage Manager directory, and any S3-compatible storage is the recommended option for data.

GlusterFS

  • GlusterFS is a distributed file system.

  • GlusterFS supports replication and failover.

Supersedes 1.5

MariaDB Enterprise ColumnStore 5 supersedes MariaDB Enterprise ColumnStore 1.5 and includes the changes in MariaDB Enterprise ColumnStore 1.5.3.