VASA Provider: Large number of bindVirtualVolume and unbindVirtualVolume API calls lead to high CPU utilization
Applies to
- ONTAP Tools for VMware vSphere (OTV) 9.11 and earlier
- VASA Provider
Issue
When a large number of virtual machines are powered on or powered off this triggers two types of API calls to VASA Provider (VP):
- unbindVirtualVolume
- bindVirtualVolume
With VASA Provider 9.11 and earlier, a large number of these bind / unbind API threads may accumulate and drive up CPU utilization on the OTV appliance.
When monitoring the VASA Provider "Right Now" page (https://<OTV>:9083/rightnow), you see 100s of inflight bind / unbind calls:
From the OTV systemshell, running top shows vpserver (the VASA Provider service) is what is driving the high CPU utilization: