VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />
Obviously, if congestion begins to occur, higher latencies will also be observed.<br />
Sustained congestion is not normal and in most cases congestion should be close to<br />
zero. Smaller values for congestion are better.<br />
What is outstanding I/O (OIO)?<br />
When a virtual machine requests for certain I/O to be performed (reads or writes),<br />
these requests are sent to storage devices. Until these requests are complete they<br />
are termed outstanding I/O. This metric explains how many operations are waiting<br />
on Virtual SAN, SSD cache, I/O controller and disks. Large amounts of outstanding<br />
I/O can have an adverse effect on the device latency. Storage controllers that have a<br />
large queue depth can handle higher outstanding I/Os. For this reason, VMware only<br />
qualifies storage controllers with a significantly high queue depth, and does not<br />
support controllers with low queue depth values. Smaller numbers for OIO are<br />
better.<br />
What is latency standard deviation (stddev)?<br />
The latency stddev (standard deviation) graph gives an idea of how wide the latency<br />
spread is at any given point. It is a measurement of the standard deviation of all<br />
latency times, which shows the variability of latency across all I/O requests. Lower<br />
standard deviation implies that the latency is predictable and well bounded<br />
(workload is running in a steady state). Higher values indicate that latency is<br />
fluctuating heavily and possibly warrants further investigation.<br />
What to look for in the <strong>VSAN</strong> Client view?<br />
If this view shows any unexpected performance, in other words, any of the charts<br />
are underlined in red, the next step is to drill down further to understand where<br />
performance issues may be coming from.<br />
It is important to understand that due to the distributed nature of <strong>VSAN</strong>, any host<br />
may access data from disks on any of the other hosts in the cluster. Therefore any<br />
host in the <strong>VSAN</strong> cluster may cause any performance issue seen in the <strong>VSAN</strong> Client<br />
view. The next steps will be:<br />
<br />
<br />
To check the ‘<strong>VSAN</strong> disks’ view to learn more about any bottlenecks that<br />
might be attributed to the disks (either magnetic disk or flash device/SSD).<br />
Check the ‘VMs’ centric view to see how individual disks and hosts are<br />
contributing to a virtual machines performance.<br />
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 2 0 8