Installing and Configuring a Single Server System
After the MariaDB ColumnStore servers have been setup based on the Preparing for Installations Document and the required MariaDB ColumnStore Packages have been Installed, run the script 'postConfigure' to complete the configuration and installation. This Article shows how to install on a single server system.
If installing a single combined functionality server with no plans to add additional servers, Single Node should be chosen.
Going from one configuration to another will require a re-installation of the MariaDB ColumnStore software.
The following is a transcript of a typical run of the MariaDB ColumnStore configuration script. Plain-text formatting indicates output from the script and bold text indicates responses to questions. After each question there is a short discussion of what the question is asking and what some typical answers might be. You will not see these discussions the running the actual configuration script.
NOTE: You can install MariaDB ColumnStore as a root user or non-root user. This is based on how you setup the servers based on "Preparing for Installation Document". If installing as root, you need to be logged in as root user in a root login shell. If you are installing as non-root, you need to be logged in as a non-root user that was setup in the "Preparing for Installation Document".
Common Installation Examples During postConfigure, this first question will be asked. Select 1 for a Single Server Install
Select the type of server install [1=single, 2=multi] (1) > 1
Running postConfigure as root user:
/usr/local/mariadb/columnstore/bin/postConfigure
Running postConfigure as non-root user:
export COLUMNSTORE_INSTALL_DIR=/home/guest/mariadb/columnstore export LD_LIBRARY_PATH=/home/guest/mariadb/columnstore/lib:/home/guest/mariadb/columnstore/mysql/lib/mysql /home/guest/mariadb/columnstore/bin/postConfigure -i /home/guest/mariadb/columnstore
This is the MariaDB Columnstore System Configuration and Installation tool. It will Configure the MariaDB Columnstore System and will perform a Package Installation of all of the Servers within the System that is being configured.
IMPORTANT: This tool should only be run on the Parent OAM Module which is a Performance Module, preferred Module #1
Prompting instructions:
Press 'enter' to accept a value in (), if available or Enter one of the options within [], if available, or Enter a new value
Setup System Server Type Configuration
There are 2 options when configuring the System Server Type: single and multi
'single' - Single-Server install is used when there will only be 1 server configured on the system. It can also be used for production systems, if the plan is to stay single-server.
'multi' - Multi-Server install is used when you want to configure multiple servers now or in the future. With Multi-Server install, you can still configure just 1 server now and add on addition servers/modules in the future.
Select the type of System Server install [1=single, 2=multi] (2) > <<creole>>**1**<</creole>>
Performing a Single Server Install. Enter System Name (columnstore-1) > mymcs1 <</code>> Notes: You should give this system a name that will appear in various Admin utilities, SNMP messages, etc. The name can be composed of any number of printable characters and spaces.
===== Setup High Availability Data Storage Mount Configuration ===== There are 2 options when configuring the storage: internal and external 'internal' - This is specified when a local disk is used for the DBRoot storage. High Availability Server Failover is not Supported in this mode 'external' - This is specified when the DBRoot directories are mounted. High Availability Server Failover is Supported in this mode. Select the type of Data Storage [1=internal, 2=external] (1) > <Enter>
Notes: Choosing internal and using softlinks to point to an externally mounted storage will allow you to use any format (i.e., ext2, ext3, etc.).
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of dbroot IDs assigned to module 'pm1' (1) > 1
Notes: The installer will set up the number of dbroot directories based on this answer.
===== MariaDB ColumnStore SNMP-Trap Process Check ===== MariaDB ColumnStore is packaged with a SNMP-Trap Process. If the system where MariaDB ColumnStore is being installed already has SNMP-Trap Process running, then you have the option of disabling MariaDB ColumnStore's SNMP-Trap Process. Additional information: Not having the MariaDB ColumnStore SNMP_trap Process will affect the generation of MariaDB ColumnStore Alarms and associated SNMP Traps. Please reference the MariaDB ColumnStore Installation Guide for Installs for addition information. MariaDB ColumnStore SNMP-Trap Process is enabled, would you like to disable it (y,n) [n] > <Enter>
Notes: If you choose to disable (y) but still want the MariaDB ColumnStore snmp-traps to be generated and sent to a Network Management System, please see the “Error! Reference source not found.” section below.
===== Setup the Network Management System (NMS) Server Configuration ===== This would be used to receive SNMP Traps from MariaDB Columnstore. 0.0.0.0 defaults to not sending off the system Enter IP Address(es) of NMS Server (0.0.0.0) > <Enter> ===== Performing Configuration Setup and MariaDB Columnstore Startup ===== NOTE: Setting 'NumBlocksPct' to 50% Setting 'TotalUmMemory' to 25% of total memory (Combined Server Install maximum value is 16G). Value set to 4G
Notes: The default maximum for a single server is 16Gb.
Running the MariaDB Columnstore MySQL setup scripts post-mysqld-install Successfully Completed post-mysql-install Successfully Completed Starting MariaDB ColumnStore Database Platform Starting MariaDB ColumnStore Database Platform, please wait......... DONE System Catalog Successfully Created MariaDB ColumnStore Install Successfully Completed, System is Active Enter the following command to define MariaDB ColumnStore Alias Commands . /usr/local/mariadb/columnstore/bin/columnstoreAlias Enter 'mcsmysql' to access the MariaDB Columnstore MySQL console Enter 'mcsadmin' to access the MariaDB Columnstore Admin console
MariaDB Columnstore Memory Configuration
During the installation process, postConfigure will set the 2 main Memory configuration settings based on the size of memory detected on the local node.
The 2 settings are in the MariaDB Columnstore Configuration file, /usr/local/mariadb/columnstore/etc Columnstore.xml. These 2 settings are:
'NumBlocksPct' - Performance Module Data cache memory setting TotalUmMemory - User Module memory setting, used as temporary memory for joins
On a Single Server Install, this is the default settings:
NumBlocksPct - 50% of total memory TotalUmMemory - 25% of total memory, default maximum the percentage equal to 16G
The user can choose to change these settings after the install is completed, if for instance they want to setup more memory for Joins to utilize. On a single server or combined UM/PM server, it is recommended to not have the combination of these 2 settings over 75% of total memory.