MariaDB ColumnStore System Operations and Configuration
Contents
System Status
Viewing system status
The system status shows the status of the system and all equipped servers. To view the system status, use getSystemStatus command in mcsadmin, or simply use mcsadmin getSystemStatus from the operating system prompt.
Example: # mcsadmin getSystemStatus getsystemstatus Sat Jun 11 01:01:22 2016 System columnstore-1 System and Module statuses Component Status Last Status Change ------------ -------------------------- ------------------------ System ACTIVE Fri Jun 10 01:50:46 2016 Module pm1 ACTIVE Fri Jun 10 01:50:43 2016
The table below shows the available system and server statuses.
| Status | Definition |
|---|---|
| Active | The system, server, or Network Interface Card (NIC) is available to process database requests |
| Auto Disabled | Disabled as a result of a server failure. |
| Auto Init | Auto initialization mode during a fault recovery. |
| Auto Offline | The system or server is offline due to a fault. |
| Busy_Init | The module/system is performing an initialization task at startup time before going to the ACTIVE state. |
| Degraded | The server is active, but the performance is degraded. A server is degraded when a NIC is not working. |
| Down | Communication failure. |
| Failed | A stop/start/restart request for the system or a server failed. |
| Initial | Initial state after a system reboot or install and before any action is taken. |
| Man Disabled | Disabled as a result of executing the altersystem-disableModule command. |
| Man Init | Manual initialization mode during a start or restart command. |
| Man Offline | The system or server was taken offline with the stop or shutdown command. |
| Up | Successfully communicating. |
When all servers are active, then the system status is active. If one server is Man Offline and the others are active, the system is Man Offline. All equipped servers must be active before the system is shown as active.
Viewing process status
To view the process status, use getProcessStatus command in mcsadmin, or simply use mcsadmin getProcessStatus from the operating system prompt. The table below shows the available system and server statuses.
Example: [myusr@srv1 ~]# mcsadmin getProcessStatus getprocessstatus Sat Jun 11 00:59:09 2016 MariaDB Columnstore Process statuses Process Module Status Last Status Change Process ID ------------------ ------ --------------- ------------------------ ---------- ProcessMonitor pm1 ACTIVE Fri Jun 10 01:50:04 2016 2487 ProcessManager pm1 ACTIVE Fri Jun 10 01:50:10 2016 2673 SNMPTrapDaemon pm1 ACTIVE Fri Jun 10 01:50:16 2016 3534 DBRMControllerNode pm1 ACTIVE Fri Jun 10 01:50:20 2016 3585 ServerMonitor pm1 ACTIVE Fri Jun 10 01:50:22 2016 3625 DBRMWorkerNode pm1 ACTIVE Fri Jun 10 01:50:22 2016 3665 DecomSvr pm1 ACTIVE Fri Jun 10 01:50:26 2016 3742 PrimProc pm1 ACTIVE Fri Jun 10 01:50:28 2016 3770 ExeMgr pm1 ACTIVE Fri Jun 10 01:50:32 2016 3844 WriteEngineServer pm1 ACTIVE Fri Jun 10 01:50:36 2016 3934 DDLProc pm1 ACTIVE Fri Jun 10 01:50:40 2016 3991 DMLProc pm1 ACTIVE Fri Jun 10 01:50:45 2016 4058 mysqld pm1 ACTIVE Fri Jun 10 01:50:22 2016 2975
The table below shows the supported process states.
| Status | Definition |
|---|---|
| Active | The process is fully functional. |
| Auto Init | Auto initialization mode during a fault recovery |
| Auto Offline | The process is offline due to a fault. |
| Busy Init | The process is performing an initialization task at startup time before going to the ACTIVE state. |
| Failed | A stop/start/restart request for a process failed. |
| Hot Standby | The process is functional in a standby/ready state in case a failover occurs. |
| Initial | State after a system reboot or install and before any action is taken |
| Man Init | Manual initialization mode during a start or restart command |
| Man Offline | The process was taken offline with the stop or shutdown command. |
| Standby Init | Manual initialization mode during a start or restart command of a Hot Standby process. |
Operations
Stopping the system
To stop the system use, stopSystem command in mcsadmin, or simply use mcsadmin stopSystem from the operating system prompt.
Stopping the system stops the storage engine database processes. The process that supports the Management Console and System Alarms remain active.
Starting the system or modules
To start the system, use startSystem command in mcsadmin, or simply use mcsadmin startSystem from the operating system prompt
Restarting the system
To restart the system, use restartSystem command in mcsadmin, or simply use mcsadmin restartSystem from the operating system prompt
Shutting down the system
To shut down the system completely including storage engine database processes as well as the process that supports management console and System Alarms, use shutdownSystem command in mcsadmin, or simply use mcsadmin shutdownSystem from the operating system prompt
Disabling System Modules
A System Module can be disabled when is system is ACTIVE or OFFLINE. To disable a module, use alterSystem-disableModule module_id command in mcsadmin, or simply use mcsadmin alterSystem-disableModule module_id from the operating system prompt.
Example: mcsadmin alterSystem-disablemodule PM2, PM3
The modules PM2 and PM3 will be stopped and disabled.
_Note_: Disabling a module may result in data loss if the data is local to the PM. If the data is SAN mounted, the dbroots would need to be moved to other PMs. Please see “Moving DBRoots” of this guide for more information on moving DBRoots.
Enabling System Modules
To enable a module, use alterSystem-enableModule module_id command in mcsadmin, or simply use mcsadmin alterSystem-enableModule module_id from the operating system prompt.
Example: mcsadmin alterSystem-enablemodule PM2, PM3
The modules PM2 and PM3 will be enabled and started.
Switch Parent OAM Module
Parent OAM Module is the Performance Module that monitors the over all system including all the UM and PM nodes and their status, as well as handle PM node failover. In a running system with more than 1 PM node there will be 2 Parent OAM Module - an Active Parent and a Standby Parent.
To switch a module to the Standby Parent, use switchParentOAMModule in mcsadmin, or simply use mcsadmin switchParentOAMModule from the operating system prompt. The Standby Parent OAM Module will become active.
To switch a module to a specific module: use switchParentOAMModule module_id on mcsadmin, or simply use mcsadmin switchParentOAMModule module_id from the operating system prompt.
Example: switchParentOAMModule pm3
The Performance-Module 3 will become the active Parent OAM Module
System Configuraiton
Viewing Network Configuration
To view network configuration of all the nodes and their status use getSystemNetworkConfig on mcsadmin, or simply use mcsadmin getSystemNetworkConfig from the operating system prompt.
Example: [myusr@srv1 ~]mcsadmin getSystemNetworkConfig getsystemnetworkconfig Sat Jun 11 01:34:55 2016 System Network Configuration Module Name Module Description NIC ID Host Name IP Address Status ----------- ------------------------- ------ --------- --------------- ------------ pm1 Performance Module #1 1 localhost 127.0.0.1 UP
Viewing Module Configuration
To view network configuration of all the nodes and their status use getModuleConfig on mcsadmin, or simply use mcsadmin getModuleConfig from the operating system prompt.
[myusr@srv1 ~]mcsadmin getModuleConfig getmoduleconfig Sat Jun 11 01:51:37 2016 Module Name Configuration Module 'um1' Configuration information ModuleType = um ModuleDesc = User Module #1 ModuleIPAdd NIC ID 1 = 10.100.7.80 ModuleHostName NIC ID 1 = srvhst2 ModuleIPAdd NIC ID 2 = 10.100.107.81 ModuleHostName NIC ID 2 = srvhst2b Module 'pm1' Configuration information ModuleType = pm ModuleDesc = Performance Module #1 ModuleIPAdd NIC ID 1 = 10.100.7.10 ModuleHostName NIC ID 1 = srvhst1 DBRootIDs assigned = 1
