I don't know if someone's mentioned it yet but TravisCI is also not running on the commits that do show up on git, in Houston
Status.github.com: “We're failing over a data storage system”
71–80 of 173 posts
Re: Status.github.com: “We're failing over a data storage system”
#72I'm really looking forward to the post mortem that comes out of this (if it does). I always learn a lot from reading those.
A post-mortem from Microsoft ? nfw
GitHub are not part of Microsoft yet, the deal has only just been approved. They are still totally separate, and will be for some considerable time.
Also Microsoft post plenty of postmortems, like this detailed one from the VSTS outage in Sept. https://blogs.msdn.microsoft.com/vsoservice/?p=17485
Re: Status.github.com: “We're failing over a data storage system”
#73I think they started running over Microsoft infrastructure. ;)
Re: Status.github.com: “We're failing over a data storage system”
#74Earlier quoted context omitted.
It is to ensure that the updates get mirrored onto twitter, where exact duplicates can't be posted.
Isn't it enough to delete the older tweet? Or maybe just add a timestamp to the message. Off-Topic: If it's not possible to write a twit with the exact text from a deleted twit, then a way to prove someone wrote a twit and then deleted it would be to have them try to write it again.
Deleting tweets is a terrible workaround. Once github start tweeting and people start linking to those tweets they can't go ahead and delete them 50 minutes later..
Re: Status.github.com: “We're failing over a data storage system”
#75Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are? In the enterprise space, a 'data storage system' could be an Array or a SAN or a lightpath etc, with usually quite long failover times. For an org like GitHub I'd think more like an object store (an Array-of-Hosts, if you will) or whatever storage mechanism holds their database files. Do they self host t…
> Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are?
To be fair, you can't call it trolling without knowing for sure that the problem hasn't been caused by Azure-related part of the infrastructure. Looking forward to reading the post-mortem.
Re: Status.github.com: “We're failing over a data storage system”
#76Obligatory: to all the people running around like de-headed chickens: this is what happens when you focus on a service not on the dvcs.
Your code and your wiki (if you use it) are already in git repos. If the industry moved forward on issues in dvcs repos, you have another central point of failure removed.
You also have less hassle to work across dvcs hosts, which is exactly why GitHub would never embrace this.
Re: Status.github.com: “We're failing over a data storage system”
#77Wonder if GitHub is "too useful to fail" at this point. As in, most people and companies won't switch git repo providers unless GitHub is down for many days at a time during the work week.
Transition to BitBucket or gilab is one click away. Companies surely will move if incentives are there.
Not when you use third party integrations. Like when using Travis for CI, and Travis doing your deploy.
Re: Status.github.com: “We're failing over a data storage system”
#78Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are? In the enterprise space, a 'data storage system' could be an Array or a SAN or a lightpath etc, with usually quite long failover times. For an org like GitHub I'd think more like an object store (an Array-of-Hosts, if you will) or whatever storage mechanism holds their database files. Do they self host t…
> Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are? To be fair, you can't call it trolling without knowing for sure that the problem hasn't been caused by Azure-related part of the infrastructure. Looking forward to reading the post-mortem.
It is incredibly unlikely that there is any Azure in the production infrastructure. The acquisition is too recent for big changes like that.
Re: Status.github.com: “We're failing over a data storage system”
#79Earlier quoted context omitted.
> Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are? To be fair, you can't call it trolling without knowing for sure that the problem hasn't been caused by Azure-related part of the infrastructure. Looking forward to reading the post-mortem.
It is incredibly unlikely that there is any Azure in the production infrastructure. The acquisition is too recent for big changes like that.
It's actually so recent GitHub hasn't even been acquired yet. That's going to happen some time next year.
Re: Status.github.com: “We're failing over a data storage system”
#80Earlier quoted context omitted.
> Before all the trolling about Microsoft starts up, does anyone have current information on what these systems are? To be fair, you can't call it trolling without knowing for sure that the problem hasn't been caused by Azure-related part of the infrastructure. Looking forward to reading the post-mortem.
It is incredibly unlikely that there is any Azure in the production infrastructure. The acquisition is too recent for big changes like that.
[deleted]