Live data from Hacker News

20+ hour outage due to EC2/EBS on BitBucket

bitbucket.org

1–10 of 48 posts

Re: 20+ hour outage due to EC2/EBS on BitBucket

#6
post #4

Everything fails. Design systems that minimize the impact failures have on your customers. Moving to another provider isn't going to fix the problem. Data like this should be stored in more than one place.

In reality, replicating across two clouds is difficult and expensive. It's quite possible that Bitbucket wouldn't exist at all if they had used such an architecture.

Re: 20+ hour outage due to EC2/EBS on BitBucket

#8

Ugh. I am working on the next gen architecture for our site, and I wanted to focus on hosting it in a cloud - but all these outages give me no confidence that cloud-based hosting is really all that ready for primetime yet.

IHMO AWS Windows instances may not be ready for prime time. This issue seems not to affect Linux based instances.

There are other cloud providers like the YC favorite, SliceHost - I have no direct experience with them but may soon try them out.

Re: 20+ hour outage due to EC2/EBS on BitBucket

#9
post #5

I'm here to answer questions if there are any (I run Bitbucket.)

What are you thinking in terms of movement / failover at this point?

We've been contacted by several hosting providers, and right now, Rackspace seems pretty nice.

The problem isn't that we don't have failover here, it's that we store all repositories on a single EBS volume. This has worked great for us in the past, but as of last night, that volume has become virtually unavailable to us. It doesn't matter which instance we mount it on, the throughput we get from it is excruciating.

If, or at this point--when, we move, the disk architecture will look different, and general failover will be less of an issue.

Amazon has for the past 8-10 hours been investigating the issue, and we're left pretty dumbfounded as of to what has happened exactly. I'll summarize everything in a blog post once the chaos is over.

Post reply on HN