The Ultimate Guide to High Availability with MariaDB

MariaDB ColumnStore software upgrade 1.2.0 Alpha to 1.2.1 Beta

You are viewing an old version of this article. View the current version here.
  1. MariaDB ColumnStore software upgrade 1.2.0 Alpha to 1.2.1 Beta
    1. Changes in 1.2.1 and later
      1. Non-Distributed is new Fault in postConfigure
      2. Non-root user sudo setup
    2. Setup
      1. Columnstore.xm / my.cnf
      2. MariaDB root user database password
    3. Choosing the type of upgrade
      1. Root User Installs
      2. Upgrading MariaDB ColumnStore using RPMs tar package
      3. Upgrading MariaDB ColumnStore using RPM Package Repositories
    4. Initial download/install of MariaDB ColumnStore binary package
    5. Upgrading MariaDB ColumnStore using the DEB package
      1. Upgrading MariaDB ColumnStore using DEB Package Repositories
      2. Non-Root User Installs
    6. Initial download/install of MariaDB ColumnStore binary package

MariaDB ColumnStore software upgrade 1.2.0 Alpha to 1.2.1 Beta

Changes in 1.2.1 and later

Non-Distributed is new Fault in postConfigure

Default install type by postConfigure is now Non-Distributed, It was Distributed in the 1.1.X releases. But this doesnt effect upgrades. It will perform the upgraded based on how to previous 1.1.x package was installed. If it was install as Distributed, then the upgrade will also be done as Distributed. Same goes for Non-Distributed.

Non-root user sudo setup

Non-root user installation has been changed related to the sudo configuration setup. Prior to 1.2.1, the user was required to setup sudo to allow all access to root level commands got the user where MariaDB Columnstore was installed. Starting in 1.2.1, sudo configuration is not required in some installations. In others, there a limit command set that needs to be setup. This is document here:

https://mariadb.com/kb/en/library/preparing-for-columnstore-installation-121/#update-sudo-configuration-if-needed-by-root-user

The sudo configuration can be changed during the upgrade process once you have uninstalled the current version of MariaDB Columnstore and before you started to install the 1.2.1 and later versions.

Setup

Columnstore.xm / my.cnf

Both Columnstore.xml and my.cnf modifications you manually made are not automatically carried forward on an upgrade. These modifications will need to be incorporated back into Columnstore.xml and my.cnf once the upgrade has occurred.

The previous configuration file will be saved as /usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave. The previous configuration file will be saved as /usr/local/mariadb/columnstore/mysq/my.cnf.rpmsave.

MariaDB root user database password

If you have specified a root user database password (which is good practice), then you must configure a .my.cnf file with user credentials for the upgrade process to use. Create a .my.cnf file in the user home directory with 600 file permissions with the following content (updating PASSWORD as appropriate):

[mysqladmin] 
user = root
password = PASSWORD

Choosing the type of upgrade

As noted on the Preparing guide, you can installing MariaDB ColumnStore with the use of soft-links. If you have the softlinks be setup at the Data Directory Levels, like mariadb/columnstore/data and mariadb/columnstore/dataX, then your upgrade will happen without any issues. In the case where you have a softlink at the top directory, like /usr/local/mariadb, you will need to upgrade using the binary package. If you updating using the rpm package and tool, this softlink will be deleted when you perform the upgrade process and the upgrade will fail.

Root User Installs

Upgrading MariaDB ColumnStore using RPMs tar package

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

Download the package mariadb-columnstore-1.2.0-1-centos#.x86_64.rpm.tar.gz to the PM1 server where you are installing MariaDB ColumnStore. Shutdown the MariaDB ColumnStore system: 

# mcsadmin shutdownsystem y
  • Unpack the tarball, which will generate a set of RPMs that will reside in the /root/ directory. 
# tar -zxf mariadb-columnstore-1.2.0-1-centos#.x86_64.rpm.tar.gz
  • Upgrade the RPMs. The MariaDB ColumnStore software will be installed in /usr/local/. 
# rpm -e --nodeps $(rpm -qa | grep '^mariadb-columnstore')
# rpm -ivh mariadb-columnstore-*1.2.0*rpm
  • Run postConfigure using the upgrade option, which will utilize the configuration from the Columnstore.xml.rpmsave 
# /usr/local/mariadb/columnstore/bin/postConfigure -u

For RPM Upgrade, the previous configuration file will be saved as:

/usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave

Upgrading MariaDB ColumnStore using RPM Package Repositories

The system can be upgrade when it was previously installed from the Package Repositories. This will need to be run on each module in the system

Additional information can be found in this document on how to setup and install using the 'yum' package repo command:

https://mariadb.com/kb/en/library/installing-mariadb-ax-from-the-package-repositories

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

Shutdown the MariaDB ColumnStore system: 

# mcsadmin shutdownsystem y
  • Uninstall MariaDB ColumnStore Packages 
# yum remove mariadb-columnstore*
  • Install MariaDB ColumnStore Packages 
# yum --enablerepo=mariadb-columnstore clean metadata
# yum install mariadb-columnstore*

NOTE: On the non-pm1 module, start the columnstore service

# /usr/local/mariadb/columnstore/bin/columnstore start
  • Run postConfigure using the upgrade and non-distributed options, which will utilize the configuration from the Columnstore.xml.rpmsave 
# /usr/local/mariadb/columnstore/bin/postConfigure -u -n

For RPM Upgrade, the previous configuration file will be saved as:

/usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave

Initial download/install of MariaDB ColumnStore binary package

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

  • Download the package into the /usr/local directory -mariadb-columnstore-1.2.0-1.x86_64.bin.tar.gz (Binary 64-BIT)to the server where you are installing MariaDB ColumnStore.
  • Shutdown the MariaDB ColumnStore system: 
# mcsadmin shutdownsystem y
  • Run pre-uninstall script 
# /usr/local/mariadb/columnstore/bin/pre-uninstall
  • Unpack the tarball, in the /usr/local/ directory. 
# tar -zxvf mariadb-columnstore-1.2.0-1.x86_64.bin.tar.gz
  • Run post-install scripts 
# /usr/local/mariadb/columnstore/bin/post-install
  • Run postConfigure using the upgrade option, which will utilize the configuration from the Columnstore.xml,rpmsave 
# /usr/local/mariadb/columnstore/bin/postConfigure -u

Upgrading MariaDB ColumnStore using the DEB package

A DEB upgrade would be done on a system that supports DEBs like Debian or Ubuntu systems.

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

  • Download the package into the /root directory

mariadb-columnstore-1.2.0-1.amd64.deb.tar.gz

(DEB 64-BIT) to the server where you are installing MariaDB ColumnStore.

  • Shutdown the MariaDB ColumnStore system: 
# mcsadmin shutdownsystem y
  • Unpack the tarball, which will generate DEBs. 
# tar -zxf mariadb-columnstore-1.2.0-1.amd64.deb.tar.gz
  • Remove, purge and install all MariaDB ColumnStore debs 
# cd /root/
# dpkg -r  $(dpkg --list | grep 'mariadb-columnstore' | awk '{print $2}')
# dpkg -P  $(dpkg --list | grep 'mariadb-columnstore' | awk '{print $2}')

# dpkg --install mariadb-columnstore-*1.2.0-1*deb
  • Run postConfigure using the upgrade option, which will utilize the configuration from the Columnstore.xml,rpmsave 
# /usr/local/mariadb/columnstore/bin/postConfigure -u

Upgrading MariaDB ColumnStore using DEB Package Repositories

The system can be upgrade when it was previously installed from the Package Repositories. This will need to be run on each module in the system

Additional information can be found in this document on how to setup and install using the 'apt-get' package repo command:

https://mariadb.com/kb/en/library/installing-mariadb-ax-from-the-package-repositories

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

Shutdown the MariaDB ColumnStore system: 

# mcsadmin shutdownsystem y
  • Uninstall MariaDB ColumnStore Packages 
# apt-get remove mariadb-columnstore*
  • Install MariaDB ColumnStore Packages 
# apt-get update
# sudo apt-get install mariadb-columnstore*

NOTE: On the non-pm1 module, start the columnstore service

# /usr/local/mariadb/columnstore/bin/columnstore start
  • Run postConfigure using the upgrade and non-distributed options, which will utilize the configuration from the Columnstore.xml.rpmsave 
# /usr/local/mariadb/columnstore/bin/postConfigure -u -n

For RPM Upgrade, the previous configuration file will be saved as:

/usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave

Non-Root User Installs

Initial download/install of MariaDB ColumnStore binary package

Upgrade MariaDB ColumnStore as user root on the server designated as PM1:

  • Download the package into the /home/'non-root-user" directory

mariadb-columnstore-1.2.0-1.x86_64.bin.tar.gz (Binary 64-BIT)to the server where you are installing MariaDB ColumnStore.

  • Shutdown the MariaDB ColumnStore system: 
# mcsadmin shutdownsystem y
  • Run pre-uninstall script 
# $HOME/mariadb/columnstore/bin/pre-uninstall --installdir=/home/guest/mariadb/columnstore
  • Make the sudo changes as noted at the beginning of this document
  • Unpack the tarball, which will generate the $HOME/ directory. 
# tar -zxvf mariadb-columnstore-1.2.0-1.x86_64.bin.tar.gz
  • Run post-install scripts 
# $HOME/mariadb/columnstore/bin/post-install --installdir=/home/guest/mariadb/columnstore
  • Run postConfigure using the upgrade option, which will utilize the configuration from the Columnstore.xml,rpmsave 
# $HOME/mariadb/columnstore/bin/postConfigure -u -i /home/guest/mariadb/columnstore

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.