Graylog2 / Graylog2/graylog-s3-lambda
Current release causes excessive timeouts
- Dominant language
- Java
- Stars
- 13
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I had a version of graylog-s3-lambda that was created via a Cloudflare ticket and updated by Graylog engineers.
This version was based on version 1.0.1.
[graylog-s3-lambda-060821netty4.1.65-1.0.1.jar.zip](https://github.com/Graylog2/graylog-s3-lambda/files/7898698/graylog-s3-lambda-060821netty4.1.65-1.0.1.jar.zip)
After updating from the attached jar file, there are significant timeouts with retrieving files.
It doesn't look like the logs are not being sent but because of issues with flushing, the process times out and repeats twice before shutting down. This effectively triples the cost of the lambda function.
Any thoughts on what might be the issue?
I've attached DEBUG level log files for a timeout process within AWS.
[debug.log](https://github.com/Graylog2/graylog-s3-lambda/files/7898832/debug.log)
Contributor guide
Assessment
This issue has not been assessed yet.