Skip to main content
NetApp Knowledge Base

CONTAP-502174: object-store put-rate-limit's values are not persistant across reboots

Views:
16
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Issue

  • The storage aggregate object-store put-rate-limit show settings are not persistent across reboots.
  • After a takeover/giveback/update/reboot, the value is reset back to the default -1B value:

 
cluster1::*> storage aggregate object-store put-rate-limit modify -node cluster1-01 -put-rate-bytes-limit 1GB
cluster1::*> storage aggregate object-store put-rate-limit show
Node            Put Rate Limit (B/s)
--------------- ------------------
cluster1-01     1GB
cluster1-02     -1B
cluster1::*> sto fail takeover -ofnode cluster1-01
  (storage failover takeover)
Warning: A takeover will be initiated. When the partner node reboots, a giveback will be automatically initiated. Do you want to continue? {y|n}: y

 
After reboot:
cluster1::*>  storage aggregate object-store put-rate-limit show
Node            Put Rate Limit (B/s)
--------------- ------------------
cluster1-01     -1B
cluster1-02     -1B
2 entries were displayed.
 

 

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.