-
Notifications
You must be signed in to change notification settings - Fork 26
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
streams: nil record returned by aws-sdk-go? #27
Comments
mumoshu
added a commit
to mumoshu/awsbeats
that referenced
this issue
May 28, 2018
mumoshu
added a commit
to mumoshu/awsbeats
that referenced
this issue
May 28, 2018
mumoshu
added a commit
that referenced
this issue
May 31, 2018
…e, plus Stream+Firehose+S3 support (#31) * fix(streams): Handle nil record(s) returned by aws-sdk-go Ref #27 * fix(doc,example): Filebeat docker example was referring invalid tag * fix(streams): Fix panicing on a retry Turns out awsbeats was calling `batch.RetryEvents` on different data and timing. Revise the implementation according to the [official beat outputs](https://github.com/elastic/beats/blob/c4af03c51373c1de7daaca660f5d21b3f602771c/libbeat/outputs/elasticsearch/client.go#L234) Fixes #29 * Support for Kinesis DataStreams->Firehose->S3 pieplines * Improve error propagation and not give up retrying too aggressively * Add tests * More fixes to actually trigger retry on failure. Tested with invalid AWS credential
I believe this is addressed in #31. Closing until it reproduces with actual problem(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I occasionally see interesting errors like this:
In theory, this happens only when there is at least one
nil
insiderecords
inprocessFailedDeliveries
:I can hardly believe it there's such a bug in aws-sdk-go, but to gather information regarding the issue, I'd like to handle
nil
here and emit some logs for our note.The text was updated successfully, but these errors were encountered: