[MCOL-4938] Disable/enable mariadb-columnstore systemd unit installing/removing CMAPI package Created: 2021-12-06 Updated: 2021-12-10 Resolved: 2021-12-10 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | cmapi-1.5 |
| Fix Version/s: | cmapi-1.6 |
| Type: | Task | Priority: | Minor |
| Reporter: | Roman | Assignee: | Roman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2021-15, 2021-16 |
| Description |
|
One can start MCS directly calling systemctl start mariadb-columnstore or via CMAPI. When CMAPI is installed one must not start MCS directly using mariadb-columnstore unit b/c what it does interferes with CMAPI starting procedures. This might bring cluster into unusable state. Here is the simplest example, mariadb-columnstore unit starts mcs-workernode@1, mcs-dmlproc and mcs-ddlproc units on a secondary node where they don't belong. CMAPI package must effectively disable mariadb-columnstore systemd unit when it is installed and re-enabled if needed when it is removed from the system. CMAPI/MCS upgrade procedures must be taken into account. |
| Comments |
| Comment by Roman Navrotskiy [ 2021-12-06 ] |
|
I can offer mask/unmask systemd unit: https://github.com/mariadb-corporation/mariadb-columnstore-cmapi/pull/132 |
| Comment by Daniel Lee (Inactive) [ 2021-12-09 ] |
|
Build tested: 6.2.2-1 (#3464), cmapi 1.5 (#567) For a single node installation, if the cmapi package is installed, one must setup a one-node cluster using the cmapi commands and start it. Otherwise, the stack would end up in DBRM read-only state. One way to avoid this is not to install the cmapi package. |