1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
- The invocation mode of Amazon MQ integrates lambda and is synchronous. So Retry attempts option does not matter in this case[1].
- Lambda does not support custom redelivery policies. The doc[2] indicates that:
Instead, Lambda uses a policy with the default values from the Redelivery Policy page on the Apache ActiveMQ website[3], with maximumRedeliveries set to 5.
The default value from the Redelivery Policy page on the Apache ActiveMQ website is 6 now. Anyway, the value is always greater than 4.
[1]https://docs.aws.amazon.com/lambda/latest/dg/with-mq.html
[2]https://docs.aws.amazon.com/lambda/latest/dg/with-mq.html#services-mq-params
[3]https://activemq.apache.org/redelivery-policy
con risposta 4 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
So if I wanted to do a custom redelivery policy using the plugin, I'd need to consume messages myself from the queue? Do you know if another service like step functions or SNS allows for this? I just want a way to configure lambda execution based on a queue (with redeliveries and DLQ).
I'm also seeing behaviour different than the values in the policy page, I'm seeing retries being executed many more times than 6 times and the delay is much shorter than 1000 ms.
AWS SQS is a queue service. and It can set Maximum receives and and DLQ[1].
And SQS integrated lambda has its retry behavior, you can reference this doc[2].
[1]https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue.html
[2]https://docs.aws.amazon.com/zh_cn/lambda/latest/operatorguide/sqs-retries.html
If my answer is useful, adopting it is an encouragement for me,thanks~