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

Github major service outage

status.github.com

Post reply on HN
Print view View original

71–80 of 82 posts

Re: Github major service outage

#71

Post by coherentpony »

Anderkent wrote: post #58
saraid216 wrote: post #56

Earlier quoted context omitted.

The problem is mostly that people fail to actually do this.

Until github goes down, and then they run `git remote add friend ssh://coworkers-workstation//path/to/repo` and push code to each other until github comes back up.

Well, pushing to someone else's local copy is a little harsh, since that copy probably won't be bare. Also git will slap your wrists if you try to do that. Instead, the coworker should pull from you. This is why GitHub's calls them pull requests.

Re: Github major service outage

#72

Post by icebraining »

coherentpony wrote: post #71
Anderkent wrote: post #58

Earlier quoted context omitted.

Until github goes down, and then they run `git remote add friend ssh://coworkers-workstation//path/to/repo` and push code to each other until github comes back up.

Well, pushing to someone else's local copy is a little harsh, since that copy probably won't be bare. Also git will slap your wrists if you try to do that. Instead, the coworker should pull from you. This is why GitHub's calls them pull requests .

Or you can push to a different remote branch, and then they can merge it with their master.

Re: Github major service outage

#73

Post by IanCal »

ianstormtaylor wrote: post #51
phaer wrote: post #45

Earlier quoted context omitted.

Yes, there is nothing wrong with using Github, but with using only Github as your git remote. Git (in theory) makes it easy to use multiple servers. Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers plus higher availability if Github goes down; just use your other remotes. Is there a git tool to share your remotes in a repository? One could use a distributed issue t…

"Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers ..." It's crazy how GitHub's entire product is so easily marginalized by comments like this. I don't know if you meant to do it, but I think it is a serious problem with hacker culture. It's the kind of thinking that tricks startups into "knowing" they can do a better job than established competitors in spaces they…

You may have misunderstood the comment (or I have).

I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).

Re: Github major service outage

#74

Post by tadfisher »

IanCal wrote: post #73
ianstormtaylor wrote: post #51

Earlier quoted context omitted.

"Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers ..." It's crazy how GitHub's entire product is so easily marginalized by comments like this. I don't know if you meant to do it, but I think it is a serious problem with hacker culture. It's the kind of thinking that tricks startups into "knowing" they can do a better job than established competitors in spaces they…

You may have misunderstood the comment (or I have). I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).

> Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers

Re: Github major service outage

#75

Post by [deleted] »

bgentry wrote: post #53
josh2600 wrote: post #48

Earlier quoted context omitted.

Hey, are you seriously defending 3 9's of uptime? That's abysmal. Github, if they're honest about their 12 month uptime levels would be lucky to be a single 9 service. Their uptime is Terrible with a capital T. But you know what? Until there's something better everyone is going to keep using them, right? Great services with values that are hard to find become damn near irreplaceable even with terrible uptime. This is…

I agree with the rest of your comment, but... a single nine service? You think they have 36.5 full days of downtime yearly, 3 full days monthly, 16.8 hours weekly, or 2.4 hours downtime every day? That's certainly not the case. Not to mention that often when they have issues it only affects a subset of customers. https://en.wikipedia.org/wiki/Nines_(engineering)

[deleted]

Re: Github major service outage

#76

Post by elviejo »

justizin wrote: post #23
appplemac wrote: post #20

Earlier quoted context omitted.

Yes, but Github is not just about Git hosting, it's about all those awesome social tools. If you use Issues as the main bug tracker, for example, you've got a problem.

Please point me at your distributed issue tracker project. I'd love to contribute!

Also http://www.onveracity.com/ offers distributed version control, and distributed tickets, and wiki.

Re: Github major service outage

#77

Post by qhoc »

We mainly used github and one of their last updates, our entire repository turned to blank. Nada, no file, no wiki, nothing... We emailed support and tweeted their account. After one week, someone replied asking "is there problem still there?" I thought that was funny in term of how immature this company is. They eventually fixed it after like 2 weeks by restoring the backup database.

Anyways, Github is nice. Use it with caution. It cannot be full blown Enterprise ready grade service yet.

Re: Github major service outage

#78

Post by phaer »

tadfisher wrote: post #74
IanCal wrote: post #73

Earlier quoted context omitted.

You may have misunderstood the comment (or I have). I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).

> Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers

That was indeed badly phrased. I was meaning some scripts to manage multiple remotes and sync (sets of) them between your different team members. So you could have your code (and maybe dumps of githubs issue tracker) on your server and still use github when they are up and running.

Re: Github major service outage

#79

Post by blantonl »

nknighthb wrote: post #52
leedo__ wrote: post #49

Earlier quoted context omitted.

Last I investigated Galera it lacked support for query caching. Over 50% of our queries are cache hits, so it made it hard to justify using Galera over a normal master+slave setup. However I could see it being useful for setups where a single server can't handle the load (we average 300 queries/sec on a single server with lots of room to spare.)

They still disable the query cache, but MySQL's query cache generally isn't considered all that great a thing anyway, so few people care. You're better off making judicious use of Redis or memcached. The biggest win for Galera is high-availability that actually works with minimal effort. (I've never experienced a high-availability solution not based on multi-master/all-nodes-hot principles that didn't cause more prob…

but MySQL's query cache generally isn't considered all that great a thing anyway

You've never had to prime a query cache on a MySQL server, have you? :)

Re: Github major service outage

#80

Post by IanCal »

tadfisher wrote: post #74
IanCal wrote: post #73

Earlier quoted context omitted.

You may have misunderstood the comment (or I have). I don't think they were saying that a few scripts and utilities would get you what github offers. I think they were saying with some scripts you could automatically fall over to another mirror when github goes down, then switch back when it's up (updating the repo on github when it's available again).

> Add some scripts/utilities and you get Github with all their "social" stuff, wikis and issue trackers

Sometimes you need to read the entire sentence for it to make sense.

The word "add" here is important, as it's talking about having github and something else. So you get github (with all their social stuff...) AND what the scripts add, which is more reliability.

Post reply on HN