Subject VCS CRITICAL V-16-1-50086 Mem usage on host is 92%
If you are not using the BiggestAvailable failover policy, you can suppress the warnings in the following ways:
MemThresholdLevel
Determines the threshold values for memory utilization based on which various levels of logs are generated.
The notification levels are Critical, Warning, Note, and Info, and the logs are stored in the file engine_A.log.
If the Warning level is crossed, a notification is generated.
The values are configurable at a system level in the cluster.
For example, the administrator may set the value of MemThresholdLevel as follows:
HostMeters
Indicates the parameters (CPU, Mem, or Swap) that are currently metered in the cluster.
Type and dimension: string-keylist
Default: HostMeters = {"CPU", "Mem", "Swap"}
You can configure this attribute in main.cf.
The keys must be one or more from CPU, Mem, and Swap.
You cannot modify the value at run time.
The cluster has to be shutdown (possibly with -force) and the main.cf file must be manually modified.
Example:
cluster clusfalcon (
UserNames = { admin = hKLdKFkHLgLLjTLfKI }
Administrators = { admin }
UseFence = SCSI3
HacliUserLevel = COMMANDROOT
HostMeters = { CPU, Swap }
)
server101# haclus -value HostMeters
CPU Swap
Applies To
The issue only affects VCS HostMonitor running on the Linux platform for VCS 6.1, 6.2 and 7.0
At the time of this writing, the HostMonitor agent Memory Monitor doesn't take into account the kernel buffers and cache when reporting the memory usage on Linux.
A fix is included in InfoScale 7.0.1 and Storage Foundation 6.2.1. The HostMonitor has been enhanced to take into account the kernel buffers and cache.