Skip to main content
NetApp Knowledge Base

Can we enable placement rebalancing in ONTAP 9.16.1 or 9.16.0?

Views:
66
Visibility:
Public
Votes:
0
Category:
asa-r2
Specialty:
CORE
Last Updated:

Applies to

  • ASA r2 9.16.0 
  • ASA r2 9.16.1

Answer

  • Yes, the balanced placement is already enabled by default in ONTAP 9.16.1. but full workload / dynamic rebalancing cannot be enabled in 9.16.1.
  • Only ONTAP 9.17.1 and above support fully automatic workload rebalancing (dynamic space balancing).
For ASA r2 systems running ONTAP releases 9.16.0 and 9.16.1, where no dynamic rebalancing is allowed, the workload placement might lead to one aggregate full situation as noted below between the HA Pairs:
Aggregate               kbytes       used      avail capacity  
rootFA_1_p0_i1       403724160   33952952  369771208       8%  
dataFA_2_p0_i1      4037241600 4037241600          0     100%  
rootFA_3_p0_i1       403724160   38504416  365219744      10%  
dataFA_4_p0_i1      4037241600   16312676 4020928924       0%  
  • It is recommended to upgrade the cluster to ONTAP 9.17.1:
    • Upgrading the cluster to ONTAP 9.17.1 will help rebalance the workload between the HA pairs.
    • Beginning with ONTAP 9.17.1, ONTAP automatically rebalances workloads across the nodes in an ASA r2 system HA pair to optimize performance.
  • For example, if space utilization on one node increases to 70% while utilization on its HA partner is only 30%, ONTAP moves space to the node which is running out of space to prevent the node from running out of space.
  • Because the nodes of the HA pair share the same storage availability zone, workload rebalancing is a copy-free operation with no impact on performance.
Automatic workload rebalancing is enabled by default 14 days after either upgrading to ONTAP 9.17.1 or initializing a new ONTAP 9.17.1 ASA r2 cluster.
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.