-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3/SQS source events fails sporadically #20314
Comments
Hmm, yeah, that is odd. I think that sort of error would be coming from the AWS SDK (similar issue, but not for S3: awslabs/aws-sdk-rust#844). You could try increasing the log level of |
same here, is anyone resolve this?
|
Also happens with S3 sink:
|
I think all of these is related about how AWS sdk handle retries and failures for AWS IAM. |
I've tried, but messages weren't more verbose in this specific part even with aws_smithy_http=trace |
Problem
I have configured s3 source and getting following error from time to time, once in a ~30-60 min
however after being in-flight 10 minutes or so, these messages with corresponding S3 objects seem to be reprocessed successfully from SQS
Configuration
also I have
logLevel: aws_smithy_http=info,vector=info
, however along with above-mentioned error message and variousvector: Beep
- there are no other informative error messages which could explain root cause of issueVersion
0.37.1
The text was updated successfully, but these errors were encountered: