[MCOL-4120] When ColumnStore package is installed with MariaDB server already running, server is left shut down after engine installation Created: 2020-06-27  Updated: 2020-07-13  Resolved: 2020-07-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.5.2
Fix Version/s: 1.5.3

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MCOL-4134 Clean and fix remaining columnstore c... Closed
Relates
relates to MCOL-4133 columnstore-post-install and mysqld Closed

 Description   

A minimal scenario:

  • on a clean CentOS 7, configure 10.5 repo and install MariaDB server package, e.g. run 

    sudo yum install MariaDB-server

    After clean installation on RPM-based systems the server isn't started automatically, it's expected; start it as

    sudo systemctl start mariadb

    Optionally, make sure it's up and running.
    Then install Columnstore engine:

    sudo yum install MariaDB-columnstore-engine

It installs without any errors, but after it's done the server is down and has to be started again manually.
It is not the case with other engines, e.g. RocksDB, where the server is restarted after the engine installation.

Buildbot is affected and currently produces a failure on 10.5 branches in a slightly different scenario of the same origin. The "minor-upgrade-all" test in buildbot installs all MariaDB packages of the last released version present in the MariaDB official repo, e.g. at this moment all MariaDB 10.5.4 packages, including Columnstore.
After the installation It starts the server explicitly.
Then it upgrades the installation using packages produced in the current build.
It expects the server to be available afterwards, but since Columnstore is among the upgraded packages and misbehaves as described above, the server remains shut down.



 Comments   
Comment by Elena Stepanova [ 2020-06-28 ]

Similar problem with debs. Scenario for Ubuntu:

  • configure apt repo to point at MariaDB 10.5.4 release;
  • run 

    sudo apt-get install mariadb-server mariadb-plugin-columnstore

    => packages are installed, server is started automatically, Columnstore is present;

  • configure apt repo to point at newer packages, recognized as 10.5.5;
  • run 

    sudo apt-get install mariadb-server mariadb-plugin-columnstore

    => packages are upgraded, but server is no longer running and needs to be started manually. The expected result is that the server is restarted after upgrade.

Comment by Ben Thompson (Inactive) [ 2020-06-30 ]

columnstore-post-install is doing pgrep for mysqld should be changed to mariadbd. script currently never sees server is running and so defaults to stopping it at completion.

Comment by Daniel Lee (Inactive) [ 2020-07-09 ]

Build verified: 1.5.3-1 (drone build #280)

Tested on Centos7.6 and Ubuntu18.04

Verified mariadbd is running after columnstore engine installation. Also verified the columnstore engine is available. mariadbd process did get restarted during columnstore engine installation.

Comment by Elena Stepanova [ 2020-07-12 ]

dleeyh,
Did you ever reproduce and observe the failure in your tests before the fix?

Comment by Roman [ 2020-07-13 ]

I'm not Daniel but yes, the issue was reproducable and introduced with MDB binaries renaming.

Generated at Thu Feb 08 02:47:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.