Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
After MCS installation has finished we must have all prerequisites to run MCS. We lack systemd units to start ExeMgr, PrimProc, WriteEngine, PrimProc, DDLProc, DMLProc and Cluster management Agent. There must be separate systemd units for all services and one cumulative to control all services at once. Here and here are the example scripts how to start MCS services. As of now there must be SKIP_OAM_INIT=1 set in the runtime environment to disable legacy OAM.
We need to test units at all supported platforms: Centos7, Debian8,9, Ubuntu 16,18. Centos8, Debian 10 should be also tested though we don't build for them yet.
Attachments
Activity
systemd units don't work in Ubuntu and I think in all other deb-based distros.
4QA
MCS now has a number of systemd units to start processes and load extent map into the memory. You can search them using systemctl list-unit-files then search for mcs.
There is a single rule-them-all unit called mariadb-columnstore to start/stop MCS.
Build verified: 1.5.0-1 (drone build 66)
[centos7:root~]# systemctl list-unit-files|grep -i mcs
mcs-controllernode.service static
mcs-ddlproc.service static
mcs-dmlproc.service static
mcs-exemgr.service static
mcs-loadbrm.service enabled
mcs-primproc.service static
mcs-storagemanager.service enabled
mcs-workernode.service static
mcs-writeengineserver.service static
[centos7:root~]# systemctl list-unit-files|grep -i mariadb
mariadb-columnstore.service enabled
mariadb.service disabled
Have been using these services this week
You will find all changes in
MCOL-3836branch