Skip to main content
NetApp Knowledge Base

vMotion Failures Due to Latency During StorageGRID Decommission

  1. Last updated
  2. Save as PDF
Views:
2
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID
  • ONTAP FabricPool clusters (ONTAP 9.16.1P8 and above)
  • NFSv3 protocol environments
  • Veeam Instant Recovery (IR) workflows
  • Large grid environments with active node decommissioning

Issue

  • Persistent Storage vMotion failures when migrating VMs from a temporary Veeam IR datastore to a production datastore using vMotion (NFSv3 protocol).
  • Failures present as timeout errors and “Filesystem timeout (Ok to retry)” messages.
  • Application slowness and backup performance issues.
  • Observed after an ONTAP upgrade.
  • Profiler and logs show high cloud/object store latency, especially during active node decommission.
  • Errors such as HTTP 500 (asyncPush error: no consumer) and 499 for GETs, high IO wait times, and disk read latency spikes (300-500ms).
  • Example log output:
    HTTPMethod=GET, HTTPStatusCode=500, Details={asyncPush error: no consumer}Filesystem timeout (Ok to retry)

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.