Skip to main content
NetApp Knowledge Base

VASA Provider: Large number of bindVirtualVolume and unbindVirtualVolume API calls lead to high CPU utilization

  1. Last updated
  2. Save as PDF
Views:
98
Visibility:
Public
Votes:
0
Category:
netapp-vasa-provider
Specialty:
virt
Last Updated:

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:

clipboard_e31d209902ba71f915af9300d76ce4c20.png

From the OTV systemshell, running top shows vpserver (the VASA Provider service) is what is driving the high CPU utilization:

clipboard_ed83ea820e935db8845cb45a455825b7b.png

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.