"VCS CRITICAL V-16-1-50086 Mem usage on host is n%" is reported by VCS HostMonitor agent

book

Article ID: 100012823

calendar_today

Updated On:

Description

Error Message

Subject VCS CRITICAL V-16-1-50086 Mem usage on host is 92%

Workarounds

If you are not using the BiggestAvailable failover policy, you can suppress the warnings in the following ways:
 

1. Increase the MemThresholdLevel to a very high value to avoid the warning.

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:

  • MemThresholdLevel={Critical=95, Warning=80, Note=75, Info=60}
  • Type and dimension: integer-association
  • Default: Critical=90, Warning=80, Note=70, Info=60

 

 

2. Disable the Host Memory monitor completely by removing it from HostMeters.

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

Cause

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.

Resolution

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.

Issue/Introduction

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.

The kernel buffers and cache are mainly used for file system I/O buffering. They are readily available to processes that demand more memory. By default the free command will include a memory usage report that is adjusted by buffers and cache. From the free manual page:
The -o switch disables the display of a "buffer adjusted" line. If the -o switch is not specified, free subtracts buffer memory from the used memory and adds it to the free memory that is reported.
# free
total used free shared buffers cached
Mem: 3891484 3131168 760316 0 196408 268276
-/+ buffers/cache: 2666484 1225000 <<< "used" and "free" are adjusted
Swap: 8388600 225092 8163508
Because the HostMonitor agent doesn't take into account the kernel buffers and cache, if the system is under heavy file system I/O load, the HostMonitor agent may log warning messages regarding high usage of host memory. But this may not reflect the actual situation.

Additional Information

ETrack: 3520211