Hacker News Reader

Comment by janson0 | Hacker News Reader

SQS is the specific service giving me a ton of trouble right now. Hope they resolve this quickly. Had rayguns about sqs all night heh.

So are they saying they are throttling SQS because of the DynamoDB issue?

View on HN

Here's the SQS Error Log right now:

3:14 AM PDT We are investigating increased error rates in the US-EAST-1 Region.

4:06 AM PDT We can confirm increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region and continue to work towards resolution.

5:07 AM PDT We can confirm increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region. As we work towards recovery, error rates may temporarily increase.

6:06 AM PDT We can confirm significantly increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region. As we work towards recovery, error rates may temporarily increase in error rates.

I have seen multi-hour SQS outages recently. I'm thinking of options for how we can go about preventing an application failure if this happens again.

* If adding to SQS fails, temporarily store the item on disk or S3, then add to SQS when it's back up?

* any other options?

I'm not sure. I think many of the other services mentioned probably rely internally on SQS, so resolving the SQS issues might resolve most of the other issues as well.

Not completely sure though whether DynamoDB would benefit from relying internally on SQS.

Yeah good point. It's something I forget sometimes that AWS uses AWS... and that even if I don't rely on a particular service specifically, a service I rely on may, in fact, rely on that service.