Skip to main content
NetApp Knowledge Base

If there are multiple backends, how does Trident select which backend to use?

  1. Last updated
  2. Save as PDF
Views:
413
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

Astra Trident

Answer

When there are multiple backends that match the request, Astra Trident chooses one of them at random in order to prevent hotspots.
 

Additional Information

Trident Backend Selection:
• Filters backends by PVC/StorageClass requirements (protocol, size, parameters, labels).
• Any backend without enough free space for the request is excluded.
• If multiple matches, Trident picks one randomly — it does not check CPU load, performance metrics, or number of existing volumes.

ONTAP Aggregate Selection:
• If aggregates are defined in the Trident backend, that aggregate is always used.
• If not, ONTAP chooses from the SVM’s aggr_list using its internal placement logic (free space, load distribution, etc.).

PVC → Aggregate Selection Flow:
1. PVC created → Trident checks StorageClass and filters eligible backends.
2. Backend chosen → If multiple remain, selection is random.
3. Aggregate chosen →
• aggregates: set in backend → Trident uses it.
• Not set → ONTAP picks from SVM’s aggr_list.

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.