Skip to main content
NetApp Knowledge Base

Does the behavior of limitAggregateUsage in the Trident backend configuration depending on other settings, like aggregate, or provisioning is thin or thick?

  1. Last updated
  2. Save as PDF
Views:
22
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes/Openshift (any version)

Answer

  • Yes, it does.
  • Whether the size of the provisioned volume is included in the calculation for limitAggregateUsage depends on whether the provisioning is thin or thick.
  • aggregate setting is not required for limitAggregateUsage.
    • If multiple aggregates are assigned to an SVM, limitAggregateUsage setting works on each aggregate individually.
    • As long as there is at least one aggregate with available capacity , that aggregate will be used for provisioning.

Additional Information

additionalInformation_text

 

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.