Skip to main content
NetApp Knowledge Base

S3 job is failing to read the data from a bucket with "HTTP Status Code=500 ErrorMsg=InternalError"

  1. Last updated
  2. Save as PDF
Views:
507
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID
  • External Load Balancer / Gateway (NGINX)
  • Spark Jobs

Issue

  • Spark job on the client end is failing to read the objects from the StorageGRID bucket with "HTTP Status Code=500 ErrorMsg=InternalError".
  • The error message can be found in bycast.log in the log bundle or under /var/local/log directory. The failure detail {asyncPush error: no consumer} indicates the client connection was lost while the StorageGRID node was returning the data to the client.

Sep 19 09:11:38 <NODE> ADE: |12561386 2430411499 S3RQ PSHD 2022-09-19T09:11:38.901474| ERROR    1880 94aa61294d2c0aae S3RQ: S3 request error (after response): connection=1663578683183367, Resource=/bucket/xxxx/optimized/production/lte/1234567890.snappy, HTTP Status Code=500, ErrorMsg=InternalError, ErrorType=Client CustomErrorMessage={<none>}, Details={asyncPush error: no consumer}

 

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.