Skip to main content
NetApp Stage KB

High CVO latency after node failover

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
Perf
Last Updated:

 

Applies to

  • Cloud Volumes ONTAP (CVO) HA
  • Azure

Issue

  • The Cloud hypervisor hosting the CVO instance rebooted, which resulted in a failover of node 01 to node 02.
  • During the failover, elevated read latency may be encountered

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.