The Ultimate Guide to High Availability with MariaDB

MariaDB ColumnStore software upgrade 1.1.6 GA 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.1.6 GA to 1.2.1 Beta
    1. Changes in 1.2.1
      1. Non-distributed is the default distribution mode in postConfigure
      2. Non-root user sudo setup
      3. Running the mysql_upgrade script
    2. Setup
      1. Columnstore.xml / my.cnf
      2. MariaDB root user database password
    3. Choosing the type of upgrade
      1. Root User Installs
      2. Upgrading MariaDB ColumnStore using the tarball of RPMs (distributed mode)
      3. Upgrading MariaDB ColumnStore using RPM Package Repositories (non-distributed mode)
    4. Upgrading MariaDB ColumnStore using the binary tarball (distributed mode)
    5. Upgrading MariaDB ColumnStore using the DEB package (distributed mode)
      1. Upgrading MariaDB ColumnStore using DEB Package Repositories (non-distributed mode)
      2. Non-Root User Installs
    6. Upgrade MariaDB ColumnStore from the binary tarball (distributed mode)

MariaDB ColumnStore software upgrade 1.1.6 GA to 1.2.1 Beta

This upgrade also applies to 1.2.0 Alpha to 1.2.1 Beta upgrades

Changes in 1.2.1

Non-distributed is the default distribution mode in postConfigure

The default distribution mode has changed from 'distributed' to 'non-distributed'. During an upgrade, however, the default is to use the distribution mode used in the original installation. The options '-d' and '-n' can always be used to override the default.

Non-root user sudo setup

Root-level permissions are no longer required to install or upgrade ColumnStore for some types of installations. Installations requiring some level of sudo access, and the instructions, are listed here: https://mariadb.com/kb/en/library/preparing-for-columnstore-installation-121/#update-sudo-configuration-if-needed-by-root-user

Running the mysql_upgrade script

As part of the upgrade process to 1.2.1, the user is required to run the mysql_upgrade script on all of the following nodes.

  • User Modules on a system configured with separate User and Performance Modules
  • Performance Modules on a system configured with separate User and Performance Modules and Local Query Feature is enabled
  • Performance Modules on a system configured with combined User and Performance Modules

mysql_upgrade should be run once the upgrade has been completed.

This is an example of how it run as root user:

/usr/local/mariadb/columnstore/mysql/bin/mysql_upgrade --defaults-file=/usr/local/mariadb/columnstore/mysql/my.cnf --force

This is an example of how it run as non-root user, assuming ColumnStore is installed under the user's home directory:

$HOME/mariadb/columnstore/mysql/bin/mysql_upgrade --defaults-file=$HOME/mariadb/columnstore/mysql/my.cnf --force

Setup

In this section, we will refer to the directory ColumnStore is installed in as <CSROOT>. If you installed the RPM or DEB package, then your <CSROOT> will be /usr/local. If you installed it from the tarball, <CSROOT> will be where you unpacked it.

Columnstore.xml / my.cnf

Configuration changes made manually are not automatically carried forward during the upgrade. These modifications will need to be made again manually after the upgrade is complete.

After the upgrade process the configuration files will be saved at:

  • <CSROOT>/mariadb/columnstore/etc/Columnstore.xml.rpmsave
  • <CSROOT>/mariadb/columnstore/mysql/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

Note, softlinks may cause a problem during the upgrade if you use the RPM or DEB packages. If you have linked a directory above /usr/local/mariadb/columnstore, the softlinks will be deleted and the upgrade will fail. In that case you will need to upgrade using the binary tarball instead. If you have only linked the data directories (ie /usr/local/MariaDB/columnstore/data*), the RPM/DEB package upgrade will work.

Root User Installs

Upgrading MariaDB ColumnStore using the tarball of RPMs (distributed mode)

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

Download the package mariadb-columnstore-1.2.1-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.1-1-centos#.x86_64.rpm.tar.gz
  • Uninstall the old packages, then install the new packages. The MariaDB ColumnStore software will be installed in /usr/local/. 
# rpm -e --nodeps $(rpm -qa | grep '^mariadb-columnstore')

# rpm -ivh mariadb-columnstore-*1.2.1*rpm
  • Run postConfigure using the upgrade option 
# /usr/local/mariadb/columnstore/bin/postConfigure -u
  • Run the mysql_upgrade script on the nodes documented above.

Upgrading MariaDB ColumnStore using RPM Package Repositories (non-distributed mode)

The system can be upgraded 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 all modules except for PM1, start the columnstore service

# /usr/local/mariadb/columnstore/bin/columnstore start
  • Run postConfigure using the upgrade and non-distributed options 
# /usr/local/mariadb/columnstore/bin/postConfigure -u -n
  • Run the mysql_upgrade script on the nodes documented above.

Upgrading MariaDB ColumnStore using the binary tarball (distributed mode)

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

  • Download the package into the /usr/local directory

mariadb-columnstore-1.2.1-1.x86_64.bin.tar.gz

  • 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.1-1.x86_64.bin.tar.gz
  • Run post-install scripts 
# /usr/local/mariadb/columnstore/bin/post-install
  • Run postConfigure using the upgrade option 
# /usr/local/mariadb/columnstore/bin/postConfigure -u
  • Run the mysql_upgrade script on the nodes documented above.

Upgrading MariaDB ColumnStore using the DEB package (distributed mode)

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

  • Download the package into the /root directory

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

  • Shutdown the MariaDB ColumnStore system: 
# mcsadmin shutdownsystem y
  • Unpack the tarball, which contains DEBs. 
# tar -zxf mariadb-columnstore-1.2.1-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.1-1*deb
  • Run postConfigure using the upgrade option 
# /usr/local/mariadb/columnstore/bin/postConfigure -u
  • Run the mysql_upgrade script on the nodes documented above.

Upgrading MariaDB ColumnStore using DEB Package Repositories (non-distributed mode)

The system can be upgraded 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 all modules except for PM1, start the columnstore service

# /usr/local/mariadb/columnstore/bin/columnstore start
  • Run postConfigure using the upgrade and non-distributed options 
# /usr/local/mariadb/columnstore/bin/postConfigure -u -n
  • Run the mysql_upgrade script on the nodes documented above.

Non-Root User Installs

Upgrade MariaDB ColumnStore from the binary tarball (distributed mode)

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

  • Download the package into the user's home directory

mariadb-columnstore-1.2.1-1.x86_64.bin.tar.gz (Binary 64-BIT)

  • Shutdown the MariaDB ColumnStore system: 
# mcsadmin shutdownsystem y
  • Run the pre-uninstall script; this will require sudo access as you are running a script from 1.1.6. 
# <CSROOT>/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 in the same place as the original installation 
# tar -zxvf mariadb-columnstore-1.2.1-1.x86_64.bin.tar.gz
  • Run post-install scripts 
# <CSROOT>/mariadb/columnstore/bin/post-install --installdir=<CSROOT>/mariadb/columnstore
  • Run postConfigure using the upgrade option 
# <CSROOT>/mariadb/columnstore/bin/postConfigure -u -i <CSROOT>/mariadb/columnstore
  • Run the mysql_upgrade script on the nodes documented above.

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.