Skip to main content
NetApp Knowledge Base

NFSv4.1 Latency During Cluster Reboot on CVO

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

Applies to

  • Cloud Volumes ONTAP (CVO)
  • NFSv4.1 protocol environments

Issue

CVO planned cluster reboots with NFSv4.1 clients experience latency or timeouts (up to 2 minutes in rare cases, but typically around 45 seconds). This is observed as increased delay in protocol takeover and LIF movement, impacting business workloads such as SAP.

Cause

  • The latency is caused by the NFSv4.1 grace period and protocol negotiation during cluster or node reboot/failover.
  • Delays may be exacerbated by high workload, aggregate fill, or ongoing root/boot snapshots.
  • This is expected behavior for NFSv4.1 clients during failover, as per protocol standards and ONTAP design.
  • A one-time 2-minute delay may occur during instance type changes or specific environmental triggers (e.g., GCP outage or plex resync).

Solution

  • Upgrade ONTAP to the latest recommended version to benefit from protocol improvements and bug fixes for NFSv4.1 latency.
  • Confirm that the observed NFSv4.1 delay during planned takeover/giveback is within protocol and ONTAP tolerance.
  • Monitor latency using qos statistics volume latency show and cluster metrics before and after reboot.
  • For critical workloads, schedule reboots during off-peak hours and inform application owners of expected NFSv4.1 grace period delays.

Partner Notes

partnerNotes_text

Additional Information

additionalInformation_text

Internal Notes

internalNotes_text

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.