Skip to content
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

feat: set maxConcurrency on LambdaWorker DLQ #92

Merged

Conversation

nemanja-kovacevic-thinkit
Copy link
Contributor

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.

@nemanja-kovacevic-thinkit nemanja-kovacevic-thinkit force-pushed the PLT-1141-set-max-concurrency-for-dlq branch 2 times, most recently from 78fa628 to 78f9b79 Compare November 20, 2024 11:27
@nemanja-kovacevic-thinkit nemanja-kovacevic-thinkit force-pushed the PLT-1141-set-max-concurrency-for-dlq branch from 78f9b79 to eacb24d Compare November 20, 2024 11:32
@nemanja-kovacevic-thinkit nemanja-kovacevic-thinkit merged commit f4d3cd9 into main Nov 20, 2024
13 checks passed
@nemanja-kovacevic-thinkit nemanja-kovacevic-thinkit deleted the PLT-1141-set-max-concurrency-for-dlq branch November 20, 2024 12:01
@talisaspire
Copy link
Collaborator

🎉 This PR is included in version 3.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants