1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Not sure why you are receiving these errors. I do not think the issue is with SQS capacity, it more looks like some issue on the client side. Maybe you should retry if this happens?
Saying that, why aren't you using EventBridge Scheduler, which can handle millions of recurring and one time events. No need for you DDB table, the function that wakes up every minute and the queue. EB Scheduler can invoke your dispatcher function directly.
Contenuto pertinente
- In che modo posso risolvere i problemi relativi a ReportBatchItemFailures della funzione Lambda SQS?AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 7 mesi fa
Thanks for your answer, I revamped my implementation to avoid sending too many message in the same lambda process and used batching to reduce SQS calls it looks like I do not have the ECONNRESET error anymore.
Unfortunately EventBridge Scheduler doesn't totally fit my needs since it has a 60-second precision and for the purpose of my application I need something closer to a 1-second precision. But maybe combined with a sleep function in the dispatcher it could do the job, I'll further dig into it to!