Skip to main content
NetApp Knowledge Base

CONTAP-733031: S3 lifecycle expiration stops midway through a large bucket and the next scan starts over

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

An ONTAP S3 bucket with an object-age expiration rule can stop expiring objects before every eligible object is removed.
  • Only part of a large bucket is expired, then the scan stops.
  • Eligible objects that were not reached remain in the bucket.
  • The next scan waits for the full scan interval. The default interval is 1 hour.
  • That next scan starts again at the beginning of the bucket instead of continuing from the last processed object.
  • Objects near the end of a large bucket can remain past the configured expiration age.
  • Object count from [vserver object-store-server bucket show] stops decreasing before expiration is finished.

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.