Skip to main content
NetApp Knowledge Base

Applications accessing ONTAP S3 buckets encounter HTTP 429 Too Many Requests responses

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

Applies to

  • AFF
  • 9.1x
  • Ontap S3

Issue

  • An application accessing an ONTAP S3 bucket reports HTTP 429 (Too Many Requests) errors during object operations.
  • The failures are accompanied by errors similar to the following:
    com.xx.xx.xxx.xx.ExecutionException: [9xxc - Send file to S3 bucket] Unknown error occurred while getting metadata of S3 Object Key 'accc-iccc-fcccs/uoccccs.csv' in Bucket 'ccccc': Too Many Requests (Service: Amazon S3; Status Code: 429; Error Code: 429 Too Many Requests; Request ID: null; S3 Extended Request ID: null; Proxy: null)
  • Application jobs intermittently fail when accessing objects in an ONTAP S3 bucket.
  • Metadata retrieval requests for S3 objects receive HTTP 429 Too Many Requests responses.
  • The issue is reported from the application side while interacting with the ONTAP S3 endpoint.
  • Object access operations may fail even though the bucket and objects remain available.
  • ONTAP logs and ASUP data did not indicate any request throttling or errors originating from the ONTAP S3 service.

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.