A Parent OAM Module in MariaDB ColumnStore is one of the performance module (PM) nodes, which in addition to query processing like other PM nodes, also monitors the overall system health, resource usage and PM node failover management. Various mcsadmin commands can be used to configure the monitoring parameters. The monitored resources are system, processes, servers, CPU usage, disk usage, RAID, memory usage, and swap space.

System monitoring configuration

Viewing system configuration

To view the system configuration, use the getSystemConfig command in mcsadmin, or simply use mcsadmin getSystemConfig from the operating system prompt.

Example:

# mcsadmin getSystemConfig
getsystemconfig Wed Mar 28 10:17:49 2016

System Configuration

SystemName = sn-perf-1
SoftwareVersion = 3.0
SoftwareRelease = 0
ParentOAMModuleName = pm1
StandbyOAMModuleName = pm2
NMSIPAddr = 0.0.0.0
ModuleHeartbeatPeriod = 1
ModuleHeartbeatCount = 3
DBRootCount = 6
DBRoot1 = /usr/local/mariadb/columnstore/data1
DBRoot2 =/usr/local/mariadb/columnstore/data2
DBRoot3 = /usr/local/mariadb/columnstore/data3
DBRoot4 = /usr/local/mariadb/columnstore/data4
DBRoot5 = /usr/local/mariadb/columnstore/data5
DBRoot6 = /usr/local/mariadb/columnstore/data6
DBRMRoot = /usr/local/mariadb/columnstore/data1/systemFiles/dbrm/BRM_saves
ExternalCriticalThreshold = 90
ExternalMajorThreshold = 80
ExternalMinorThreshold = 70
MaxConcurrentTransactions = 1000
SharedMemoryTmpFile = /usr/local/mariadb/columnstore/data1/systemFiles/dbrm/CalpontShm
VersionBufferFileSize = 1
OIDBitmapFile = /usr/local/mariadb/columnstore/data1/systemFiles/dbrm/oidbitmap
FirstOID = 3000
TransactionArchivePeriod = 10

Setting system configuration

Module heartbeats

Heartbeat monitoring occurs between modules (both UM and PM). The module heartbeat settings are the same for all modules.

1. The module heartbeat period refers to how often the heartbeat test is performed. For example, if you set the period to 5, then the heartbeat test is performed every 5 seconds.
   To set the module heartbeat period, use the setSystemConfig ModuleHeartbeatPeriod n command in mcsadmin, or simply use mcsadmin setSystemConfig ModuleHeartbeatPeriod n from the operating system prompt, where where n= number of seconds
2. The module heartbeat count refers to how many failures in a row must take place before a fault is processed. To disable heartbeat monitoring, set the period to -1.
   To set the module heartbeat count, use the setSystemConfig ModuleHeartbeatCount n command in mcsadmin, or simply use mcsadmin setSystemConfig ModuleHeartbeatCount n from the operating system prompt, where n= number of failures.

Disk threshold

Thresholds can be set to trigger an alert when file system usage crosses a specified percentage of a file system on a server. Critical, Major or Minor thresholds can be set for the disk usage for each server.

1. Minor threshold parameter: EXTERNALMinorThreshold
2. Major threshold parameter: EXTERNALMajorThreshold
3. Critical threshold parameter: EXTERNALCriticalThreshold

To disable a threshold, set it to 0.

To set a particular threshold, use the setSystemConfig <threshold parameter> n command in mcsadmin, or simply use mcsadmin setSystemConfig <threshold parameter> n from the operating system prompt, where where n= threshold limit as percentage of disk usage

Example: To set Major threshold to 80%

# mcsadmin setSystemConfig ExternalMajorThreshold 80
setsystemconfig   Sat Jun 11 03:53:08 2016

Successfully set ExternalMajorThreshold = 80

Viewing storage configuration

To view the storage configuration, use the getStorageConfig command in mcsadmin, or simply use mcsadmin getStorageConfig from the operating system prompt.

Example:

# mcsadmin getstorageconfig Wed Mar 28 10:40:34 2016

System Storage Configuration

Storage Type = internal
System DBRoot count = 6
DBRoot IDs assigned to 'pm1' = 1
DBRoot IDs assigned to 'pm2' = 2
DBRoot IDs assigned to 'pm3' = 3
DBRoot IDs assigned to 'pm4' = 4
DBRoot IDs assigned to 'pm5' = 5
DBRoot IDs assigned to 'pm6' = 6

Module monitoring configuration

For each module (PM and UM), the following resource monitoring parameters can be configured:

Alarm trigger count threshold

For an alarm, a threshold can be set for how many times the alarm can be triggered in 30 minutes. The default threshold is 100.

setAlarmConfig (alarmID#) Threshold n

(where n= maximum number of times an alarm can be triggered in 30 minutes),

Example to change Alarm ID 22's threshold to 50:

# mcsadmin setAlarmConfig 22 Threshold 50

Logging level management

There are five levels of logging in MariaDB ColumnStore.

• Critical
• Error
• Warning
• Info
• Debug

To get details about current logging configuration:

# mcsadmin getlogconfig
getlogconfig   Wed Oct 19 06:58:47 2016

MariaDB Columnstore System Log Configuration Data

System Logging Configuration File being used: /etc/rsyslog.d/49-columnstore.conf

Module    Configured Log Levels
------    ---------------------------------------
pm1       Critical Error Warning Info

The system logging configuration file referenced is a standard syslog configuration file and may be edited to enable and or disable specific levels, for example to disable debug logging and to only log at the specific level in each file:

# cat /etc/rsyslog.d/49-columnstore.conf
# MariaDb Columnstore Database Platform Logging
local1.=crit -/var/log/mariadb/columnstore/crit.log
local1.=err -/var/log/mariadb/columnstore/err.log
local1.=warning -/var/log/mariadb/columnstore/warning.log
local1.=info -/var/log/mariadb/columnstore/info.log

After making changes to this restart the syslog process, e.g:

# systemctl restart rsyslog

Log rotation and archiving are also configured by the installer and the settings for this may be found and managed similarly in the file /etc/logrotate.d/columnstore. If log files are manually deleted restart the syslog process to resume logging.