feat: set maxConcurrency on LambdaWorker DLQ #92
Merged
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.
https://techfromsage.atlassian.net/browse/PLT-1141
Problem: when replaying messages in bulk, the number of concurrent lambda’s are not controlled and this can result in a flood of concurrent lambda’s
Solution: We set the max concurrency on the lambda workers SQS trigger for the main queue. We should set the same value on the DLQ trigger.