GitHub's Website Remains Broken After a Data Storage System Failed Earlier Today (theregister.co.uk)
Github engineers are trying to repair the data storage system underpinning the code hosting website, which has been presenting users with a "What!?" error for much of the Sunday. From a report: Depending on where you are, you may have been working on some Sunday evening programming, or getting up to speed with work on a Monday morning, using resources on GitHub.com -- and possibly failing miserably as a result of the outage. From about 4pm US West Coast time on Sunday, the website has been stuttering and spluttering. Specifically, the site is still up and serving pages -- it's just intermittently serving out-of-date files, and ignoring submitted Gists, bug reports, and posts. Sometimes, it appears to be serving a read-only cache or older backup of itself, although some fresh code pushes are coming through onto the site. From the status page, it appears a data storage system died, forcing the platform's engineers to move the dot-com's files over to another box. In the meantime, some older versions of files and repos are being served to visitors and users. "We're continuing to work on migrating a data storage system in order to restore access to GitHub.com," the team said just after 5pm PT, adding in the past few minutes: "We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process."
INb4 "Microsoft Broke It!" - they've yet to actually take over. They're still waiting on government approval of the acquisition.
just signed the GitHub purchase.
Slashdot, fix the reply notifications... You won't get away with it...
"All ops staff required to use pure HoloLens interface with floating console and keyboard!"
*Github immediately convulses*
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Which data storage sytem would that be? Brand and model. I want to know so that I can think badly of it, or possibly of the persons who configured it, but most probably the vendor.
When all you have is a hammer, every problem starts to look like a thumb.
The storage system heard that it would soon be acquired by Microsoft and had a heart attack :)
When all you have is a hammer, every problem starts to look like a thumb.
A possible clue:
Moving to bare metal and federated storage on Rackspace has brought our average Rails response time to consistently under 100ms
But that post is ancient.
When all you have is a hammer, every problem starts to look like a thumb.
Microsoft would just run CHKDSK to fix it.
For what it's worth, sourceforge is still here and googlecode isn't. Probably says more about Google's baby-eating culture than anything.
When all you have is a hammer, every problem starts to look like a thumb.