Improve Lambda Merges #4735
Closed
Improve Lambda Merges #4735
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdettai
force-pushed
the
improve-lambda-merges
branch
from
21a742e to
0e2f545
Compare
rdettai
force-pushed
the
improve-lambda-merges
branch
from
0e2f545 to
a6d1f15
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Improve the actor shutdown on AWS Lambda runs so that merges go through.
How was this PR tested?
I ran the Quickwit Lambda stack with the mock data generator for a few weeks with both:
Both ran without any error and all merges were properly performed.
This test also led to opening #4734 as Cloudwatch logs costs where excessively high.