Search the VMware Knowledge Base (KB)
View by Article ID

vSAN memory or SSD congestion reached threshold limit (2071384)

  • 12 Ratings
Language Editions

Details

Summary

You receive this alert when an ESXi host that is part of a vSAN cluster determines that the internal vSAN memory (LSOM) or Flash (SSD) device has exceeded the predefined congestion threshold.

Examples of this alert are:

LSOM Memory Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 201.
LSOM SSD Congestion State: Exceeded. Congestion Threshold: 200 Current Congestion: 201.


Congestion in vSAN occurs when the I/O rate of the lower layers of the storage subsystem fails to keep up with the I/O rate of the higher layers.

Local Log Structured Object Management (LSOM) is an internal component of vSAN, that works at the physical disk level (both flash devices and magnetic disks). LSOM also handles the read caching and write buffering for the components.

SSD is a cache device for a vSAN disk group.

The LSOM memory congestion state and LSOM SSD congestion state occur when vSAN artificially introduces latencies in the virtual machines in order to slow down writes to the flash device layer or layers.

Impact

During an observed congestion period, higher virtual machine latencies occur.

Short periods of congestion might occur as vSAN uses a throttling mechanism to ensure that all layers run at the same I/O rate.

Smaller values for congestion are preferable, as higher value signifies latency. However, sustained congestion are not usual and in most cases, congestion should be close to zero.

Solution


If virtual machines perform a high number of write operations, write buffers could fill up on flash cache devices. These buffers must be de-staged to magnetic disks in hybrid configurations. De-staging can only be performed at a rate at which the magnetic disks in a hybrid configuration can handle.

Other reasons for congestion could be related to:
  • Faulty hardware
  • Corrupted or incorrectly functioning drivers or firmware
  • Insufficient I/O controller queue depths
  • Under specified  vSAN deployments
For more information, see the:

Note:
After the congestion levels falls back below the threshold, ESXi generates these types of event:

LSOM Memory Congestion State: Normal. congestion Threshold: 200 Current Congestion: 190.
LSO SSD Congestion State: Normal. Congestion Threshold: {3} Current Congestion: 190.

To monitor vSAN congestion threshold, see Adding alarms to vCenter Server for VMware vSAN monitoring (2091347).  

Additional Information

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 12 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 12 Ratings
Actions
KB: