Skip to main content
NetApp Knowledge Base

VASA Provider: VMware Snapshot operations fail with "Reached maximum split load allowed on the node" error

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

Applies to

  • ONTAP Tools for VMware vSphere 9.13 and earlier
  • VASA Provider
  • VMware vSphere vVol (virtual volumes)

Issue

VMware snapshot operations fail when:

  • The VM (which resides on a vVol datastore) has a large number of fairly large disks (20+ 2TB disks)
  • There is evidence that the volume file clone split load "Allowable Split Load" is exceeded

When troubleshooting the issue, you see the following behavior:

  1. In VASA Provider's (VP) vvolvp.log, the following 'clone-token-create' API calls fail during VP's 'prepareToSnapshotVirtualVolume' task with the following reason:

[cxf-12345:prepareToSnapshotVirtualVolume-123] NaException com.netapp.offtap3.ontap.ApiFailedException: Failed to create token for node "node01". Reason:  Reached maximum split load allowed on the node. (errno=13001)

  1. During the snapshot operation, you see a high 'Token Reserved Load' and the 'Allowable Split Load' pool is exhausted:

ss1ref::> volume file clone split load show
Node                            Max        Current    Token         Allowable
                                Split Load Split Load Reserved Load Split Load
------------------------------- ---------- ---------- ------------- ----------
node-01                            470TB         0B       466.9TB     3.06TB
node-02                            470TB         0B         378TB    92.00TB
 

 

 

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.