VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Brief explanation on RDT Assocs/Sockets/Client/Owners
Assocs: An RDT association is used to track peer-to-peer network state within
Virtual SAN.
Sockets: Virtual SAN limits how many TCP sockets it is allowed to use.
Clients: A Virtual SAN client represents the state on a host to access a Virtual SAN
object in the Virtual SAN cluster. There is no hard defined limit, but this metric is
shown to understand balance across hosts.
Owners: There is always one Virtual SAN owner for a given Virtual SAN object,
typically co-located with the Virtual SAN client that is accessing this object (if just
one). Virtual SAN owners coordinate all access to the Virtual SAN object and
implement functionality like RAID. There is no hard defined limit, but this metric is
shown to understand balance across hosts.
Brief explanation of disk components revisited
For disks, in Virtual SAN 5.5, there is a limit of 3,000 components. The output
displays the current component count and the percentage of disk being consumed.
In the Virtual SAN 6.0 output, the number of disk components is still shown as 3,000,
although we support 9,000 components per host in 6.0. The reason it is shown as
3,000 is because the cluster has not yet been updated to the v2 on-disk format; the
VSAN datastore is still running v1 on-disk format, which is the same format as
version 5.5.
It is worth revisiting components at this point as we will be looking at objects and
components closely in many of the upcoming command outputs.
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 / 88