Welcome to Kaizenlog.com If you're new here, you may want to subscribe to my RSS feed , Twitter You can contact us by using the contact form or submitting a comment. Thanks for visiting!

+—————————–

—————————————+
| Amazon Explains Why S3 Went Down                                   |
|   from the not-mere-sluttiness dept.                               |
|   posted by timothy on Saturday July 26, @17:33 (Bug)              |
|   http://news.slashdot.org/article.pl?sid=08/07/26/2113243 |
+——————————————————————–+

Angostura writes “Amazon has provided a decent write-up of the
[0]problems that caused its S3 storage service to fail for around 8 hours
last Sunday. It providers a timeline of events, the immediate action take
to fix it (they pulled the big red switch) and what the company is doing
to prevent re-occurrence. In summary: A random bit got flipped in one of
the server state messages that the S3 machines continuously pass back and
forth. There was no checksum on these messages, and the erroneous
information was propagated across the cloud, causing so much inter-server
chatter, that no customer work got done.”

Discuss this story at:
http://news.slashdot.org/comments.pl?sid=08/07/26/2113243

Links:
0. http://status.aws.amazon.com/s3-20080720.html

Popularity: 1% [?]

Listen to this podcast Listen to this podcast

Print This Post Print This Post





  • Related Posts



  • Leave a Reply

    Comment moderation is enabled. Your comment may take some time to appear.