Replies: 2 comments 1 reply
-
You could try enabling AWS debugging by setting an environment variable: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the clarification. One question though - when retrying does it raise the error when all of the retries of failed or before a retry is attempted? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using the S3 source with SQS and we've noticed we're getting quite a few network errors fetching the files from S3, mostly "TransientError: connection close before message completed". Rate is about 10 per hour at peak
Is there a way to get more verbose debugging of the AWS API calls to try and work out what the issue is? I have a vauge recollection on another thread where there was an environment variable we could set to just get verbose debugging on AWS calls but I can't recall it.
Beta Was this translation helpful? Give feedback.
All reactions