Because StoreVirtual VSA uses intelligent multipathing, in an optimal implementation each physical host would always be connected to all VSAs in the storage cluster. All VSAs will therefore be able to establish sessions with each physical host and data can be optimally distributed across nodes on writing.
Data locality is only leveraged on a site level in a HPE StoreVirtual VSA stretched cluster configuration in order to avoid high latencies.
Whether data locality is a good or a bad thing has turned into a philosophical debate. Its true that data locality can prevent a lot of network traffic between nodes, because the data is physically located at the same node where the VM resides. However, in dynamic environments where VMs move to different hosts on a frequent basis, data locality in most cases requires a lot of data to be copied between nodes in order to maintain the physical VM-data relationship. The SDS/HCI vendors today that choose not to use data locality, advocate that the additional network latency is negligible.