4 ms·
What's the extent of the damage that everybody experienced from this outage?
by bgentry 16y ago
What's the extent of the damage that everybody experienced from this outage?
- deleted 16y ago[deleted]
- blasdel 16y agoI was having %90 of my requests time out. Very little of the software I'm using handled the exceptions raised while this was happening. I checked the status page first thing, but it didn't get set to yellow for another 5 minutes after I started having problems.
- timf 16y ago> little of the software I'm using handled the exceptions raised while this was happening Are saying there is a library you are using that failed to treat a timeout as an issue at all? (if this is for SQS, may I ask what that library is?)
- blasdel 16y agoThe aws-s3 gem was throwing an exception correctly after a fairly long timeout ("We encountered an internal error. Please try again.") But none of the software that was using the aws-s3 gem or causing it to be called caught the exception. I ended up with exceptions getting thrown all over the place, mostly in views from methods on data coming out of models (Rails was catching it at the top-level as ActionView::TemplateError)
- timf 16y agoAh, thanks for explaining more.
- blantonl 16y agoI had an archive server go down because of queued up requests to send data to S3. Good lesson for us, we need to handle these types of issues better on our end.