Deploy Single-Node MariaDB Enterprise ColumnStore 1.4 with MariaDB Enterprise Server 10.4 on SLES 15¶
These instructions detail the deployment of MariaDB Enterprise ColumnStore 1.4 with MariaDB Enterprise Server 10.4 on SUSE Linux Enterprise Server 15 in a Single-node ColumnStore Deployment configuration.
These instructions detail how to deploy a single-node columnar database, which is suited for an analytical or OLAP workload that does not require high availability (HA). This deployment type is generally for non-production use cases, such as for development and testing.
MariaDB Platform Components¶
These instructions detail the deployment of the following MariaDB Platform components:
MariaDB Enterprise Server Components¶
These instructions detail the deployment of the following MariaDB Enterprise Server components:
MariaDB ColumnStore single-node deployments may require some additional configurations prior to installation.
Optimizing Linux Kernel Parameters¶
MariaDB ColumnStore performs best when certain Linux kernel parameters are optimized.
Set the relevant kernel parameters in a sysctl configuration file. For proper change management, it is recommended to set them in a ColumnStore-specific configuration file.
For example, create a
/etc/sysctl.d/90-mariadb-columnstore.conffile with the following contents:
# Increase the TCP max buffer size net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 # Increase the TCP buffer limits # min, default, and max number of bytes to use net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 65536 16777216 # don't cache ssthresh from previous connection net.ipv4.tcp_no_metrics_save = 1 # for 1 GigE, increase this to 2500 # for 10 GigE, increase this to 30000 net.core.netdev_max_backlog = 2500 # optimize Linux to cache directories and inodes vm.vfs_cache_pressure = 10 # minimize swapping vm.swappiness = 10
Set the same kernel parameters at runtime using the
$ sudo sysctl --load=/etc/sysctl.d/90-mariadb-columnstore.conf
Linux Security Module Considerations¶
It is recommended to disable the system's Linux Security Module (LSM) on each node during installation to avoid confusion and potential problems. The specific steps to disable the security module will depend on the platform.
In the Configuring the Linux Security Module section, we will configure the security module and restart it.
Disabling the Linux Security Module with SELinux (RHEL/CentOS/SLES)¶
Prior to installing MariaDB Columnstore, it is necessary to set SELinux to permissive mode:
Set SELinux to permissive mode by setting
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=permissive # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Reboot the system.
Confirm that SELinux is in permissive mode using
$ sudo getenforce
When using MariaDB ColumnStore, it is recommended to set the system's locale to UTF-8.
Set the system's locale to
$ sudo localedef -i en_US -f UTF-8 en_US.UTF-8
MariaDB Corporation provides a ZYpp package repository for SUSE Linux Enterprise Server 15.
MariaDB ColumnStore ships as a storage engine plugin for MariaDB Enterprise Server and a platform engine to handle back-end storage processes. MariaDB Enterprise Server 10.4 does not require any additional software to operate as an analytics database.
Install via ZYpp (SLES)¶
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for
customer_download_tokenin the following directions.
Configure the ZYpp package repository.
To configure ZYpp package repositories:
$ sudo zypper install wget $ wget https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup $ echo "957bc29576e8fd320fa18e35fa49b5733f3c8eeb4ca06792fb1f05e089c810ff mariadb_es_repo_setup" \ | sha256sum -c - $ chmod +x mariadb_es_repo_setup $ sudo ./mariadb_es_repo_setup --token="customer_download_token" --apply \ --mariadb-server-version="10.4"
Install MariaDB ColumnStore and package dependencies:
$ sudo zypper install MariaDB-server \ MariaDB-columnstore-platform MariaDB-columnstore-engine
Install some optional dependencies for ColumnStore:
$ sudo zypper install jemalloc
jemallocis not required, but it improves performance.
Configure MariaDB ColumnStore.
Installation only loads MariaDB ColumnStore to the system. MariaDB ColumnStore may require configuration and additional post-installation steps before the database server is ready for use.
MariaDB Enterprise Server can be configured in the following ways:
If a system variable supports dynamic changes, then it can be set on-the-fly using the SET statement.
MariaDB's packages include several bundled configuration files. It is also possible to create custom configuration files.
On RHEL, CentOS, and SLES, MariaDB's packages bundle the following configuration files:
And on RHEL, CentOS, and SLES, custom configuration files from the following directories are read by default:
Choose a configuration file in which to configure your system variables and options.
It not recommended to make custom changes to one of the bundled configuration files. Instead, it is recommended to create a custom configuration file in one of the included directories. Configuration files in included directories are read in alphabetical order. If you want your custom configuration file to override the bundled configuration files, then it is a good idea to prefix the custom configuration file's name with a string that will be sorted last, such as
On RHEL, CentOS, and SLES, a good custom configuration file would be:
Set your system variables and options in the configuration file.
They need to be set in a group that will be read by mariadbd, such as
[mariadb] log_error = mariadbd.err
Cross Engine Joins¶
When a cross engine join is executed, the ExeMgr process connects to the server using the
root user with no password by default. MariaDB Enterprise Server 10.4 will reject this login attempt by default. If you plan to use Cross Engine Joins, you need to configure ColumnStore to use a different user account and password.
Configure the Cross Engine Join credentials in the
The credentials are set in the modifying the child elements of the
For example, to configure ColumnStore to use the
cross_engineuser account to connect to the server at
<CrossEngineSupport> <Host>127.0.0.1</Host> <Port>3306</Port> <User>cross_engine</User> <Password>cross_engine_passwd</Password> </CrossEngineSupport>
Columnstore.xmlis dangerous and can have unexpected results. Do not edit this configuration unless you specifically need support for Cross Engine Joins.
firstname.lastname@example.org account needs to be created on the server after it has been started. This step is described in the Create the Cross Engine Join User section.
S3 Storage Manager¶
MariaDB ColumnStore supports using S3-compatible storage. If you want to use S3-compatible storage, then you need to configure it.
[ObjectStorage] … service = S3 … [S3] bucket = your_columnstore_bucket_name endpoint = your_s3_endpoint aws_access_key_id = your_s3_access_key_id aws_secret_access_key = your_s3_secret_key [Cache] cache_size = your_local_cache_size path = your_local_cache_path
The default local cache size is 2 GB.
The default local cache path is
Ensure that the local cache path has sufficient store space to store the local cache.
Installation of MariaDB ColumnStore and MariaDB Enterprise Server packages provides the necessary software to run the Server as a ColumnStore Instance, but additional steps are required to configure the ColumnStore storage back-end.
Stop the Server¶
MariaDB ColumnStore requires that you stop MariaDB Enterprise Server before running the post-installation scripts.
Stop the service:
$ sudo systemctl stop mariadb
Disable the service, so that it does not start up automatically:
$ sudo systemctl disable mariadb
columnstore-post-installscript to provision the system to host the storage back-end:
$ sudo columnstore-post-install
MariaDB ColumnStore provides a post-configuration script to configure the ColumnStore Instance.
Run the postConfigure script on the Server:
$ sudo postConfigure -qs
When prompted, select "single" for a single-node deployment.
When prompted, set the system name.
When prompted, select "internal" to store data on the local file system.
Once postConfigure has the information it needs, it starts MariaDB ColumnStore.
Restart the System¶
Use mcsadmin restartSystem to restart MariaDB ColumnStore to clear the cache:
$ sudo mcsadmin restartSystem y
Create the Cross Engine Join User¶
The credentials for cross engine joins were previously configured in the Cross Engine Joins section. The user account must also be created, and the user account must be granted the necessary privileges to access data.
Connect to the server using MariaDB Client using the
$ sudo mariadb
Create the user account with the CREATE USER statement:
CREATE USER 'cross_engine'@'127.0.0.1' IDENTIFIED BY "cross_engine_passwd";
Grant the user account
SELECTprivileges on all databases with the GRANT statement:
GRANT SELECT ON *.* TO 'cross_engine'@'127.0.0.1';
Configuring the Linux Security Module¶
If you stopped the Linux Security Module (LSM) on each node during installation, you can restart the module and configure it on each node.
The specific steps to configure the security module depend on the platform.
Configuring the Linux Security Module with SELinux (RHEL/CentOS/SLES)¶
After installation, SELinux can be properly configured to handle ColumnStore. This can be done while SELinux is still in permissive mode using the
To configure SELinux, you have to install the packages required for
On SLES, install the following:
$ sudo zypper install policycoreutils python3-policycoreutils
Allow the system to run under load for a while to generate SELinux audit events.
After the system has taken some load, generate an SELinux policy from the audit events using
$ sudo grep mysqld /var/log/audit/audit.log | audit2allow -M mariadb_local
If no audit events were found, then this will print the following:
$ sudo grep mysqld /var/log/audit/audit.log | audit2allow -M mariadb_local Nothing to do
If audit events were found, then the new SELinux policy can be loaded using
$ sudo semodule -i mariadb_local.pp
Set SELinux to enforcing mode by setting
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=enforcing # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
Reboot the system.
Confirm that SELinux is in enforcing mode using
$ sudo getenforce
MariaDB ColumnStore includes an administrative utility called mcsadmin, which you can use to start and stop the ColumnStore processes:
When you have MariaDB ColumnStore up and running, you should test it to ensure that it is in working order and that there were not any issues during startup.
Checking Server Status¶
Connect to the server using MariaDB Client using the
$ sudo mariadb Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 38 Server version: 10.4.13-7-MariaDB-Enterprise MariaDB Enterprise Server Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>
Checking System Status¶
Execute the mcsadmin getSystemStatus command:
$ sudo mcsadmin getSystemStatus getsystemstatus Wed Jan 8 23:44:55 2020 System columnstore-1 System and Module statuses Component Status Last Status Change ------------ -------------------------- ------------------------ System ACTIVE Wed Jan 8 23:14:14 2020 Module pm1 ACTIVE Wed Jan 8 23:14:11 2020