Slashdot Mirror
GitHub Back Online After Service Outage
The Next Web reports that GitHub — home to many open source projects — suffered (and quickly recovered from) a service outage this morning, starting around 14:00 UTC. Other than that the problem "appears to have been caused by its database server," the cause isn't clear.
But describing 14:00 as morning is a bit too much.
Actually, it would help if it was a simple database outage. However, it sounds like someone over at Github did something stupid .. .like, deleted the database itself. In that case, nothing can help.
So, sure, I use github. But... it goes down for a couple of hours and SlashDot panics? This isn't news.
meteor strike is easy to plan for -- put the data in two data centers very far apart -- East/West coast of the US is good enough
That's fine for most meteors, but what about asteroids that could destroy everything on Earth? That's why you should backup to the cloud, on another planet.
If the meteors go on strike I think we'd have known about it.
In my opion their system already handles everything quite well. I've noticed few outages (this one I only heard about because I was reading slashdot, it's sunday, I'm not even working on my project right now) and, so far, they all have recovered quickly. Moreover, due to the nature of git, the outages could even be longer and more frequent that it would still not be a big issue. The issue tracking system is a bit more critical, but I hardly think anything of great value will be lost due to the problems I've seen so far. From the perspective of one of their paying users, the only change I'd care about is lower price. The system itself is already available enough that I don't consider that an issue at all.
The most worrisome thing on github so far was when it got hacked. However, having high availability would not help in this situation. That was a one time thing. That seems to have happened once to every major service out there. If it was a regular thing, then it would be a big issue.
It's news. I've corporate partners who rely heavily on gitbub.com for access to their open source tools and even for their corporate git repositories, since they're more reliable than almost any in-house source code repository I've dealt with. This especially includes the hand-built, written by the CIO source control systems, that are surprisingly common in startups before they mature. I know companies whose automated software continuous build environments because of this, so it's certainly news.
Maybe Github shut down to...voluntarily add law enforcement backdoors. Yeah. Completely voluntarily. Totally not due to legislation by BSA bribe or anything.
You can hold down the "B" button for continuous firing.
Do what Starbucks does. Use portals to other dimensions. Why do you think they're all over the place?
I read TFA and all I got was this lousy cookie
The issue tracking system is a bit more critical
They should put each project's issues in a git repository, so that you can trivially keep them replicated on your own systems.
"Little does he know, but there is no 'I' in 'Idiot'!"
Do what Starbucks does. Use portals to other dimensions.
I thought that was just to avoid tax.
I just use Git. You know, that DECENTRALIZED source control thing.... yeah, might want to think about using it in a decentralized way, since, well, you know? That's what it is? I mean, unless you mean that all of the systems you're writing code with are collectively less reliable. Seems like PEBKAC to me. Hell, you can comment out one line in a .git config file to enable a post-update hook, and you're pretty much done setting up an "in-house source code repository".
Put it this way: If any one part of your DISTRIBUTED source control goes down for a few hours, and that's a big deal.... Then you're a fucking idiot.
If everything on earth is destroyed, all remaning github users will have no issues with the new uptimes anyway.