1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Most likely this error was caused by a network connectivity issue preventing the request from reaching the SQS service. Failures are scenarios you have to expect in distributed systems and therefore must design to mitigate or withstand. By using SQS, you can depend on the high resiliency it provides for message queuing through its built-in redundancy and durability features. CloudWatch logs will show examples of issues that have occurred that SQS has mitigated or withstood. As long as upstream callers are using retry and backoff logic with SQS, the workload should continue operating as expected.
répondu il y a 2 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans