The Ultimate Guide to High Availability with MariaDB

Installing and Configuring a Multi Server ColumnStore System - 1.2.X

You are viewing an old version of this article. View the current version here.
  1. Preparing to Install
  2. Validating Pre-Requisites are Complete
  3. MariaDB ColumnStore Multi-Server Quick Installer
    1. Example: 1 UM 1 PM Deployment as Root
    2. Example : 2 PM Combo Non Root Distributed Install
  4. MariaDB ColumnStore Custom Installation

Preparing to Install

Review the Preparing for ColumnStore Installation 1.2.x document and ensure that any necessary pre-requisites have been completed on all target servers for the ColumnStore cluster including installing the ColumnStore software packages.

Validating Pre-Requisites are Complete

The ColumnStore Cluster Tester Tool can be used to verify that the target servers are are setup correctly and report specific known errors that can cause failures or timeouts in the cluster setup scripts.

The tool should be run from the same server as the subsequent quick install and postConfigure scripts. With no arguments the script will only test the current server. Specify the other servers in the cluster using the --ippaddr argument to validate those servers are reachable and also configured correctly.

MariaDB ColumnStore Multi-Server Quick Installer

The script quick_installer_multi_server.sh provides a simple 1 step install of MariaDB ColumnStore bypassing the interactive wizard style interface and works for both root and non-root installs.

The script has 4 parameters.

  • --pm-ip-addresses=xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx : IP Addresses of PM nodes, specify current node IP as first value.
  • --um-ip-addresses=xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx : IP Addresses of other UM nodes. optional if combined node install is desired.
  • --dist-install : Optional override default to perform legacy distributed installation which also performs remote ColumnStore software installation.
  • --system-name=<name> : ColumnStore System Name, defaults to 'columnstore-1'

The script will then perform an equivalent installation to running postConfigure with the arguments: It will perform an install with these defaults:

  • System-Name : Argument given or defaults to 'columnstore-1'
  • Multi-Server Install
    • if only --pm-ip-addresses specified then combined install with number of IP Addresses nodes.
    • if both --pm-ip-addresses and --um-ip-addresses specified then seperate install with PM IP's Performance Module Nodes and UM IP's User Module Nodes.
    • Non distributed install, i.e. ColumnStore software must be pre-installed on the other nodes.
      • Legacy distributed install is used if --dist-install specified which will perform remote install of the ColumnStore software on other nodes. SSH Keys must be setup to allow passwordless login to the other nodes as the OS installation user.
  • Storage : Internal
  • DBRoot : 1 DBroot per 1 Performance Module
  • Local Query is disabled on um/pm install
  • MariaDB Replication is enabled

NOTE: The Multi-Server Quick Installer defaults to a Non-Distributed Install meaning the user is required to install the MariaDB ColumnStore on all nodes and starting the ColumnStore Server on all non-pm1 nodes before running the script.

Example: 1 UM 1 PM Deployment as Root

# /usr/local/mariadb/columnstore/bin/quick_installer_multi_server.sh --um-ip-addresses=10.128.0.4 --pm-ip-addresses=10.128.0.3

Example : 2 PM Combo Non Root Distributed Install

# /home/guest/mariadb/columnstore/bin/quick_installer_multi_server.sh --pm-ip-addresses=10.128.0.3,10.128.0.4 --dist-install

MariaDB ColumnStore Custom Installation

If you choose not to do the quick install and chose to customize the various options of installations using a wizard, you may use MariaDB ColumnStore postConfigure script. Please look at Custom Installation of Multi-Server Cluster.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.