Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was down

status.github.com

Post reply on HN
Print view View original

171–180 of 253 posts

Re: GitHub was down

#171

Post by Jason_malloC »

adventist wrote: post #150
brodock wrote: post #133

Earlier quoted context omitted.

DISCLAIMER: I work for GitLab. We have a feature to replicate GitLab to different locations (EEP). We call it "Geo", which stands for "Geographical Replication". Part of the "Geo" effort is Disaster Recovery which is under heavily development. We want with Disaster Recovery to be able to reliably promote any Secondary node to a Primary, so if your US datacenter melts down under a nuclear war, you can start working wi…

Yeah I know I'll be on vacation for a long while!

Hope it will be on the moon or in a nuclear shelter. Otherwise all that fallout may ruin your trip.

Re: GitHub was down

#172

Post by granda »

groby_b wrote: post #141
brodock wrote: post #133

Earlier quoted context omitted.

DISCLAIMER: I work for GitLab. We have a feature to replicate GitLab to different locations (EEP). We call it "Geo", which stands for "Geographical Replication". Part of the "Geo" effort is Disaster Recovery which is under heavily development. We want with Disaster Recovery to be able to reliably promote any Secondary node to a Primary, so if your US datacenter melts down under a nuclear war, you can start working wi…

If your US datacenter melts down under a nuclear war, I can guarantee that none of your devs will give a damn about contributing to the code base. You might want to modify your scenarios.

As someone interested in these scenarios, where could I find out more information about what would happen post-nuclear explosion?

Re: GitHub was down

#173

Post by tambourine_man »

tambourine_man wrote: post #82

Insert remark on why we use a centralized service for a distributed source control system, etc. No one seems to care, unfortunately

Lots of answers so I'll try to address them all here. It was a rethorical question. We know what GitHub offers. I'm not a fan of its UI, particularly on mobile, but that's beside the point.

The point is, why we failed, once more, to have a distributed solution, even when the underlying tech assumes it.

Email was the last widely successful distributed medium. And it's dying, unfortunately.

Of course centralized services are easier to implement and use. Doesn't mean we should settle.

Re: GitHub was down

#177

Post by 0xbear »

kyberias wrote: post #140
0xbear wrote: post #15

How many more can we expect before they develop appreciation for testing _before_ they push to prod?

They don't do any testing before push to prod?

It's called continuous delivery, man. Merge to master and it goes out the door automatically, even if it's busted to hell. All the cool kids are doing it.

Re: GitHub was down

#178

Post by groby_b »

granda wrote: post #172
groby_b wrote: post #141

Earlier quoted context omitted.

If your US datacenter melts down under a nuclear war, I can guarantee that none of your devs will give a damn about contributing to the code base. You might want to modify your scenarios.

As someone interested in these scenarios, where could I find out more information about what would happen post-nuclear explosion?

A lot of this is out in the open

There are active simulations going on: http://www.sciencerecorder.com/article.php?n=scientists-cond...

There are preparedness drills: http://www.independent.co.uk/news/world/americas/us-politics...

There's plenty of policy analysis: https://www.cato.org/publications/policy-analysis/social-eco...

Older .mil reports: http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA080907

There are entire books taking apart what happens in specific fields: https://www.ncbi.nlm.nih.gov/books/NBK219154/

Or you could just read disaster porn^W^W post-apocalyptic sci fi.

So, a lot depends on what kinds of info you want to find. But overall, I'd say it's not worth reading, because life's not going to be much fun. Even if you're prepared.

Re: GitHub was down

#179

Post by yebyen »

shoyer wrote: post #136
LeifCarrotson wrote: post #111

Earlier quoted context omitted.

> Maintner is short for "Maintainer"...the name of the daemon that serves the maintner data to other tools is "maintnerd". Nice work! But as is custom on HN, I'll bikeshed on the name instead of delving into the contents of the tool. Why shorten the word by just 2 letters? Is there something special about the tooling that makes 8-letter projects more desirable than 10-letter projects, or is it linked to the removal o…

I think it's a Go joke. Just be glad it's not called "m"!

Oops, instructions not clear, accidentally created another suite of build tooling called "gb"

Re: GitHub was down

#180

Post by luhn »

AlphaWeaver wrote: post #175

I saw a comment earlier mentioning that GitHub allegedly doesn't release post mortems publicly? If this is true, that's upsetting.

They have published post-mortems before, but the previous bout of downtime went unacknowledged. Maybe it's a new policy.

Here's a postmortem they did several years ago: https://github.com/blog/1261-github-availability-this-week

Post reply on HN