Configuring the Alarm Threshold Using the CLI
You can configure the alarm threshold for certain alarms. For the alarms that support threshold configuration, this topic describes the command to run to set the threshold.
- VOLUME_ALARM_INODES_EXCEEDED
- Threshold is configurable at both the cluster and the volume level.
If configured at both the cluster and volume levels, the volume level threshold overrides cluster-level threshold.
- VOLUME_ALARM_TOPOLOGY_ALMOST_FULL
- Threshold is configurable at cluster level.
- VOLUME_ALARM_QUOTA_EXCEEDED
- Threshold is configurable in volume properties.
- VOLUME_ALARM_TABLE_INDEX_LAG_HIGH
- Threshold is configurable in volume properties.
- VOLUME_ALARM_TABLE_REPL_LAG_HIGH
- Threshold is configurable in volume properties.
- VOLUME_ALARM_ADVISORY_QUOTA_EXCEEDED
- Threshold is configurable in volume properties.
- AE_ALARM_AEQUOTA_EXCEEDED
- Threshold is configurable in
ae
properties. - AE_ALARM_AEADVISORY_QUOTA_EXCEEDED
- Threshold is configurable in
ae
properties. - NODE_ALARM_TOO_MANY_CONTAINERS
- Threshold is configurable at cluster level.
This alarm is also raised when total number of containers (including snap containers) exceed 10 times the value of
pernode.numcntrs.alarm.thr
. - NODE_ALARM_NO_HEARTBEAT
- Threshold is configurable at cluster level.
- NODE_ALARM_HIGH_MFS_MEMORY
- Threshold is configurable at cluster level.
This alarm is raised when MapR File System memory consumption exceeds the threshold.
- CLUSTER_ALARM_CLUSTER_ALMOST_FULL
- Threshold is configurable at cluster level.
- CLUSTER_ALARM_LICENSE_NEAR_EXPIRATION
- Threshold is configurable at cluster level.
- CLUSTER_ALARM_TOO_MANY_SNAPSHOT_CONTAINERS
- Threshold is configurable at the cluster level by setting the value for the
cldb.snap.cntr.count.alarm.threshold
property in thecldb.conf
file. Seecldb.conf
for more information.