DR2-2086 Configure TDR Aggregator for larger message bursts #224
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
kurtismash
force-pushed
the
NOJIRA_aggregatorConfig
branch
3 times, most recently
from
b98c5b3 to
725013f
Compare
|
Tested manually on intg, the Lambda can process >6k messages within 30 seconds - although the config can pass <=10k messages into an invocation, this won't happen due to the mandatory SQS metadata that comes with each message. Not tested if the Package Builder Lambda can handle a group of 10k records. |
kurtismash
force-pushed
the
NOJIRA_aggregatorConfig
branch
from
725013f to
709098e
Compare
kurtismash
changed the title
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.
Configures the TDR Aggregation workflow to handle larger bursts of messages. It's unknown how many messages the Lambda can handle in a single invocation before timeout so I've reduced this for now - it's better to have multiple invocations build a group than an invocation timeout as the messages will keep looping in Lambda/SQS until the ingest for that asset is unlocked.