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.
- To configure at the cluster-level, run the following commands:
# /opt/mapr/bin/maprcli config save -values '{"cldb.max.inodes.volume.alarm.thresh":"<value>"}'
# /opt/mapr/bin/maprcli config save -values '{"cldb.default.max.namespace.size.mb.alarm.thresh":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"cldb.max.inodes.volume.alarm.thresh":"50000000"}'
# /opt/mapr/bin/maprcli config save -values '{"cldb.default.max.namespace.size.mb.alarm.thresh":"512000"}'
To configure at the volume-level, run the following commands:
# /opt/mapr/bin/maprcli volume modify -name <volname> -maxinodesalarmthreshold <threshold>
# /opt/mapr/bin/maprcli volume modify -name <volname> -maxnssizembalarmthreshold <threshold>
For
example,
# /opt/mapr/bin/maprcli volume modify -name testvol -maxinodesalarmthreshold 0
# /opt/mapr/bin/maprcli volume modify -name testvol -maxnssizembalarmthreshold 0
- VOLUME_ALARM_TOPOLOGY_ALMOST_FULL
- Threshold is configurable at cluster level.
- To configure, run the following command:
# /opt/mapr/bin/maprcli config save -values '{"cldb.topology.almost.full.percentage":"<value>"}'
For
example,
# /opt/mapr/bin/maprcli config save -values '{"cldb.topology.almost.full.percentage":"90"}'
- VOLUME_ALARM_QUOTA_EXCEEDED
- Threshold is configurable in volume properties.
- To configure, run the following command:
# /opt/mapr/bin/maprcli volume modify -name <volname> -quota <value>
For
example,
-
# /opt/mapr/bin/maprcli volume modify -name testvol -quota 204800
- VOLUME_ALARM_TABLE_INDEX_LAG_HIGH
- Threshold is configurable in volume properties.
- To configure, run the following command:
# /opt/mapr/bin/maprcli volume create -name <volname> -dbindexlagsecalarmthresh <value in seconds>
For
example,
# /opt/mapr/bin/maprcli volume create -name testvol -dbindexlagsecalarmthresh 60
- VOLUME_ALARM_TABLE_REPL_LAG_HIGH
- Threshold is configurable in volume properties.
- To configure, run the following command:
# /opt/mapr/bin/maprcli volume create -name <volname> -dbrepllagsecalarmthresh <value in seconds>
For
example,
# /opt/mapr/bin/maprcli volume create -name testvol -dbrepllagsecalarmthresh 50
- VOLUME_ALARM_ADVISORY_QUOTA_EXCEEDED
- Threshold is configurable in volume properties.
- To configure, run the following command:
# /opt/mapr/bin/maprcli volume modify -name <volname> -advisoryquota <value>
For example,
# /opt/mapr/bin/maprcli volume modify -name testvol -advisoryquota 450
- VOLUME_ALARM_LABEL_ALMOST_FULL
- Threshold is configurable at cluster level.
-
# /opt/mapr/bin/maprcli config save -values '{"cldb.label.almost.full.percentage":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"cldb.label.almost.full.percentage":"90"}'
The default value is 90% which means that this alarm is raised when the free storage
space on Storage Pools/Nodes with the desired label for container creation/replication
is down to 10% of the total storage space with the desired label.
- AE_ALARM_AEQUOTA_EXCEEDED
- Threshold is configurable in
ae properties.
-
# /opt/mapr/bin/maprcli entity modify -name <entityname> -type <type> -quota <value>
For example,
# /opt/mapr/bin/maprcli entity modify -name newuser -type 0 -quota 0
NOTE
The value, 0, for the type parameter in the above example represents the user
entity type.
- AE_ALARM_AEADVISORY_QUOTA_EXCEEDED
- Threshold is configurable in
ae properties.
-
# /opt/mapr/bin/maprcli entity modify -name <entityname> -type <type> -advisoryquota <value>
For example,
# /opt/mapr/bin/maprcli entity modify -name newuser -type 0 -advisoryquota 0
NOTE
The value, 0, for the type parameter in the above example represents the user
entity type.
- 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.
-
# /opt/mapr/bin/maprcli config save -values '{"pernode.numcntrs.alarm.thr":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"pernode.numcntrs.alarm.thr":"50000"}'
- NODE_ALARM_NO_HEARTBEAT
- Threshold is configurable at cluster level.
-
# /opt/mapr/bin/maprcli config save -values '{"cldb.fs.mark.inactive.sec":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"cldb.fs.mark.inactive.sec":"10"}'
- NODE_ALARM_HIGH_MFS_MEMORY
- Threshold is configurable at cluster level.
This alarm is raised when file system memory consumption exceeds the threshold.
-
# /opt/mapr/bin/maprcli config save -values '{"mfs.high.memory.alarm.threshold":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"mfs.high.memory.alarm.threshold":"110"}'
- CLUSTER_ALARM_CLUSTER_ALMOST_FULL
- Threshold is configurable at cluster level.
-
# /opt/mapr/bin/maprcli config save -values '{"cldb.cluster.almost.full.percentage":"<value>"}'
For example,
# /opt/mapr/bin/maprcli config save -values '{"cldb.cluster.almost.full.percentage":"90"}'
- CLUSTER_ALARM_LICENSE_NEAR_EXPIRATION
- Threshold is configurable at cluster level.
-
# /opt/mapr/bin/maprcli config save -values '{"mapr.license.exipry.notificationdays":"<value>"}'
-
For example,
# /opt/mapr/bin/maprcli config save -values '{"mapr.license.exipry.notificationdays":"30"}'
- 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 the
cldb.conf file. See cldb.conf for
more information.
-
NOTE
The default value is
100000000.