Sunday, 30 April 2017

Troubleshoot Memory/Disk lantency/High i/o issue

VM memory ballooning (Amount of memory being used for ballooning in a VM at the request of VM tools rises above 10% configured memory).

Excessive memory ballooning on a VM is driven by tools, and can indicate memory contention on the host. Check the other VMs on the same host for possible memory contention. Additional memory or balancing of workloads across hosts and clusters may be required. Consider the active links below for further drill down.

VM memory swap.(Amount of memory being swapped for a VM by the hypervisor rises above 10%)
Excessive memory swapping for a VM often indicates memory contention on the underyling host, and is a last resort by the hypervisor to reclaim memory. Check the other VMs on the same host for possible memory contention. Additional memory or balancing of workloads across hosts and clusters may be required. Consider the active links below for further drill down.

Host to Datastore Latency(Fires when the total latency between a host and a datastore is above 20ms)
One or more of your hosts has high storage latency going to a particular datastore - consider using the active links below to narrow this down to time spent in the host vs the SAN to pinpoint the cause of the issue


VM Disk Latency(Read or write latency to any of this VM's VMDKs has gone above 20ms)
One or more VMs have high storage latency - consider using the active links to investigate IO loading on this VM's datastore(s)

Datastore high I/O delay(Latency spent by storage I/O requests in the datastore)
The datastore total latency is averaging above 20ms. This could indicate a storage IO bottleneck on the datastore. Examine the IO of VMs using this datastore for possible rebalancing of IO loads. Consider the active links below for further drill down.

VM Phantom Snapshot Files(Finds VMSN files on the datastore that aren't listed in a Virtual Machine's snapshots)
it is possible that when some of your snapshots were removed, all associated snapshot file were not cleaned up correctly. There may be opportunities to reclaim storage by removing these files

No comments:

Post a Comment