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

Status.github.com: “We're failing over a data storage system”

news.ycombinator.com

Post reply on HN
Print view View original

151–160 of 173 posts

Re: Status.github.com: “We're failing over a data storage system”

#151

Post by radiospiel »

Ma8ee wrote: post #150
tjoff wrote: post #148

Earlier quoted context omitted.

I appreciate that they try. As a user I would never rely on those estimates, but it at least gives you a sense of what's going on and what they are doing. I take that over the more common silence or "we are working on it" any day.

Exactly. We all know not to trust that those estimates are exact, but they are much better than nothing. When they say nothing we don't know if it's half an hour, half a day or half a week.

Well, so they say it is within the hour, but we still don't know if it's half an hour, half a day or half a week.

Re: Status.github.com: “We're failing over a data storage system”

#152

Post by owl57 »

hiccuphippo wrote: post #50
Fuzzwah wrote: post #32

Earlier 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.

Re: off-topic: You have to do it fast. You certainly can tweet a lot of identical tweets if you aren't in a hurry: there is a "Rock in the forest"[1] that tweets "Nothing happened today" (in Russian) every day for several years, and most of the time the text is exactly the same. Interestingly enough, the time of tweet varies widely from day to day, so it looks like a human or a program specifically made to imitate one.

[1] https://twitter.com/kamen_v_lesu

Re: Status.github.com: “We're failing over a data storage system”

#153

Post by [deleted] »

simonjgreen wrote: post #133
r_singh wrote: post #107

Earlier quoted context omitted.

Fair questions. We're a company making WISP/ISP software here in India and our cloud (hosted) offering is also hosted on servers at our office itself[1]. Our infra manages hundreds of thousands of internet subscribers in India. We're a small tech company with 25-30 people or so, with linux kernel experts who have experience of running software on questionable hardware so that service providers can take internet to ne…

What do you make out of curiosity? I run an ISP in the UK.

[deleted]

Re: Status.github.com: “We're failing over a data storage system”

#154

Post by megakid »

I'm trying to add a new user to my organisation (Monday morning, new joiners...!) and despite getting confirmations I purchased another seat, I cannot invite them. Or when I do, those seats are gone, guess it's down to which data store I'm hitting on each request.

Re: Status.github.com: “We're failing over a data storage system”

#156

Post by jhabdas »

ComputerGuru wrote: post #39

I can't add comments to pull requests("you can't do that right now") and any commits pushed to branches are not updating updating the visible status in the web interface, no are newly created branches showing up. However, if you navigate to a new commit directly with its SHA (so you can share it with someone if you really want), it'll show up (so they're just not being indexed). EDIT: Obligatory "that's what happens…

come get https://git.habd.as/comfusion/high-tea

Re: Status.github.com: “We're failing over a data storage system”

#157

Post by akx »

OJFord wrote: post #124
samontar wrote: post #85

Earlier quoted context omitted.

If you’re paying for GHE you don’t have any trouble. That’s delivered as an appliance you host.

No it isn't: https://enterprise.github.com/features#pricing

Yes it is. https://enterprise.github.com/faq#faq-3

Re: Status.github.com: “We're failing over a data storage system”

#158

Post by codedokode »

Cthulhu_ wrote: post #101
r_singh wrote: post #91

Just a few weeks ago my organization was in the position of choosing a version control platform for our repos. I'm so glad we went ahead with self hosted gitlab. We installed it on a CentOS server at our premise, SSL'd via Let's encrypt, I've even set up a dedicated gitlab runner to use Gitlab CI for continuous delivery and so far the testing is progressing pretty smoothly. All this for $0. Update: I agree, gitlab an…

What did the server cost? How many hours did you spend on it? What's your SLA? Who will be woken up at night when there's an outage? What's your backup and recovery procedure? I mean kudos to you for setting it up but it's a bit naive to believe it's better than a hosted solution right away.

There is a big difference though: self-hosted Gitlab won't kick them out:

> GitHub has the right to suspend access to all or any part of the Website or your Account at any time, with or without cause, with or without notice, effective immediately.

https://help.github.com/articles/github-corporate-terms-of-s...

Re: Status.github.com: “We're failing over a data storage system”

#159

Post by deadbunny »

Grue3 wrote: post #127
ToFab123 wrote: post #98

Earlier quoted context omitted.

Plus cost of nobody can work because their single server crashed

Git is a distributed system. People can work if they want to, but it's certainly a convenient excuse to not be working.

Sure, but the tooling around git isn't. Hard to do things if you can't make PRs, which trigger tests, which trigger builds, which trigger test deployments, which trigger tests, etc...

Re: Status.github.com: “We're failing over a data storage system”

#160

Post by deadbunny »

onion2k wrote: post #144
r_singh wrote: post #91

Just a few weeks ago my organization was in the position of choosing a version control platform for our repos. I'm so glad we went ahead with self hosted gitlab. We installed it on a CentOS server at our premise, SSL'd via Let's encrypt, I've even set up a dedicated gitlab runner to use Gitlab CI for continuous delivery and so far the testing is progressing pretty smoothly. All this for $0. Update: I agree, gitlab an…

I'm so glad we went ahead with self hosted gitlab. You say that now but if you're at the sort of scale where you might have the same issue Github is having you'll be a lot less glad someone else isn't fixing it. Especially if it's 3am. On a Saturday. In the middle of your vacation. Gitlab is awesome but it's not invincible. Problems happen regardless of what solution you pick. I'm happy to pay Github to resolve them…

I think you've forgotten this is HN, a place where operational issues are "easy", till they happen. Then they realize they might actually need to hire someone who has a clue what their doing when it comes operations that don't involve turning it off and on again.
Post reply on HN