- Más nuevo
- Más votos
- Más comentarios
Thank you for the link to the SLA, but it only talks about uptime, for which there was no downtime because the message was received by SQS and eventually delivered, albeit after 5 minutes. I was referring to message latency SLAs. For example SQS agrees to deliver all received messages that has no delay specified within 3s or something to that extent.
I would raise a support case too, except that I'm on the basic support plan and I cannot open technical support cases. I could pay 3% of my billed amount to upgrade my support plan, but I don't really need any technical guidance. I just would like to know if this is a bug/issue on SQS and report it in hopes it would get resolved. I would be happy to provide a few relevant message IDs so a technical support specialist can investigate further.
So far, no errors. No downtime notices on my personal health dashboard and no errors from SQS. I have other messages on other queues being processed and other messages on the same queue coming in just fine.
Are you seeing any errors when the delays occur? FYI the SQS SLA is on our website.
In this case I would raise a support case; talk the team about when this is occurring and try to determine what the root cause is.
I agree with @kgston and there is no mention of response time or latency in the SLA link. Amazon talks high about SQS scalability but this doesn't make sense if low latency can't be guaranteed. For several of our SQS usages in Asia Pacific (Mumbai) / ap-south-1 we are experiencing such high latencies (b/w 1 to 5 min) for approx 1% of send requests. About 10% would range in 500ms to 1s and this is when using connection pool. It is desirable to have a guarantee of under 300ms at least.
Contenido relevante
- OFICIAL DE AWSActualizada hace 7 meses
- OFICIAL DE AWSActualizada hace 7 meses