Πτώση του Amazon S3Τεχνολογία » Internet και ISPs » Web Sites - 16/02/2008
Σύμφωνα με πολλά site, η μέχρι τώρα θεωρητικά πιο αξιόπιστη υπηρεσία για storage δεδομένων, το S3 του Amazon, φαίνεται να είχε πέσει για τουλάχιστον μισή ώρα. Οι αναφορές είναι πάρα πολλές και κάποιες από αυτές έχουν μπει στην πρώτη σελίδα του digg.com. Φυσικά υπάρχει ανάλογο θέμα και στα επίσημα forum του Amazon.
Φυσικά το forum έχει γεμίσει μηνύματα όπως:
I´m really afraid to use S3 service now. My company choose to work with Amazon because of it´s reliability. We host more than 30,000 images from the number 2 TV station in Brazil. Now we are having several problems because of this S3 issues.Οι υπεύθυνοι της υπηρεσίας γράψανε στο forum:
Quick note to keep everyone up to date. The team continues to be heads down focused on getting to root cause on this morning’s problem. One of our three geographic locations for S3 was unreachable beginning at 4:31 a.m. PST and was back to near normal performance at 6:48 a.m. PST (a small number of customers experienced intermittent issues for a short period thereafter). Though we're proud of our uptime track record over the past two years with this service, any amount of downtime is unacceptable and we won't be satisfied until it's perfect.Και λίγο αργότερα:
Here’s some additional detail about the problem we experienced earlier today.Όλη αυτή η κατάσταση δεν είναι καθόλου καλή για το Amazon, αφού χαλάει την εικόνα της αξιοπιστίας των web services της...
Early this morning, at 3:30am PST, we started seeing elevated levels of authenticated requests from multiple users in one of our locations. While we carefully monitor our overall request volumes and these remained within normal ranges, we had not been monitoring the proportion of authenticated requests. Importantly, these cryptographic requests consume more resources per call than other request types.
Shortly before 4:00am PST, we began to see several other users significantly increase their volume of authenticated calls. The last of these pushed the authentication service over its maximum capacity before we could complete putting new capacity in place. In addition to processing authenticated requests, the authentication service also performs account validation on every request Amazon S3 handles. This caused Amazon S3 to be unable to process any requests in that location, beginning at 4:31am PST. By 6:48am PST, we had moved enough capacity online to resolve the issue.
As we said earlier today, though we're proud of our uptime track record over the past two years with this service, any amount of downtime is unacceptable. As part of the post mortem for this event, we have identified a set of short-term actions as well as longer term improvements. We are taking immediate action on the following: (a) improving our monitoring of the proportion of authenticated requests; (b) further increasing our authentication service capacity; and (c) adding additional defensive measures around the authenticated calls. Additionally, we’ve begun work on a service health dashboard, and expect to release that shortly.
The Amazon Web Services Team
|Tags: Amazon, s3, web services, alexa, development.
Προσθήκη άρθρου σε: Freestuff | Del.icio.us | | | | ForaCamp (top)