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

Gitlab.com was experiencing elevated error rates for Git, Web, and API

status.gitlab.com

Post reply on HN
Print view View original

71–80 of 94 posts

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#71

Post by tomxor »

the_duke wrote: post #55
tomxor wrote: post #43

Earlier quoted context omitted.

> Maybe its time to setup a self-hosted backup VCS and not depend entirely on GitHub/GitLab web. I've been wanting to do this for some time purely for git hosting (don't care about CI at all) but wasn't sure about how to make it failover... Personally i'd be happy with a headless git server, but that's not fair on everyone else who wants the GUI to browse and organise stuff, so I want gitlab etc to deal with that. Wh…

If you want transparent failover you need to use your own domain for the repo URL. In case of a failure you (or some automatic job) would have to change the DNS record. Gitlab has a repo mirroring feature [1]. But of course you'd also need to sync users public keys. Downtimes are so infrequent and relatively short that this isn't worth the effort for me. You can instead set up a read-only mirror so people can at leas…

Thanks this is useful to know

> Downtimes are so infrequent and relatively short that this isn't worth the effort for me.

That's essentially the same conclusion I keep coming too, occasionally it has hit me when I go to push something but rarely has it blocked me or anyone else from continuing to work.

> You can instead set up a read-only mirror so people can at least still pull and browse the code

Yeah, this I need to do eventually just for peace of mind as a more automated backup solution. At least I don't have to care about failover.

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#72

Post by SkyPuncher »

gilfoyle wrote: post #51

Gitlab is a great service and a great alternative to github and bitbucket. But it has been quite flaky over many years and it's quite surprising they haven't prioritised system stability over everything else. https://twitter.com/gitlabstatus Gitlab has been a fully remote proponent going back a few years and these persistent reliability issues add some doubt to that model - even if there might be altogether other iss…

Fully remotes has nothing to do with it.

My company is full remote and we don't have these issue.

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#74

Post by tester34 »

rataata_jr wrote: post #57
makeworld wrote: post #38

Earlier quoted context omitted.

Oh come on

He has a point, priorities under MS ownership.

haha I wanted write comment like "since MS bought git the amount of crashes per week has increased"

but I guess I'm too late to the party!

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#75

Post by irateswami »

INTPenis wrote: post #33

I love Gitlab because I love open source and competition but Gitlab either on-prem or gitlab.com has been having growing pains ever since I started using it around 2015. And it seems to be related to scaling because it's always iffy problems like higher error rates or jobs not executing. Either way, I love our on-prem Gitlab. It's free and it hosts over 200 projects, Gitops and the whole shebang. I'm just now beginni…

My company does on-prem gitlab as well, and it's pretty fantastic. We're in the beginning stages of migrating off of Azure DevOps but so far we're wowed by the features.

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#76

Post by ing33k »

pbalau wrote: post #66
ing33k wrote: post #60

/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.

We are using bitbucket atm and I can't fathom a reason to move, care to elaborate?

mainly for DevOps related features.

https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab/ ( marketing page, but mostly valid points )

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#78

Post by robotmay »

qeternity wrote: post #37

We switched from self-hosted to gitlab.com a couple months back and the migration has been extremely disappointing. Pushing commits often hangs completely, and we've had a number of smaller downtimes/degradations in recent weeks that have been super disruptive. Having been Gitlab users since our inception, we're now seriously considering Github (I know - grass is always greener).

Any chance you could drop me some details about pushes hanging? I'm an engineer in the source code team doing a lot of performance work and I might be able to correlate it with known issues or investigate it further. I know it's a bit awkward to get data after-the-fact but just some links to the problem repos would be useful. I might not be very useful if it's related to network/hardware issues but I do work in that aspect of the software at least.

You can tag me on an issue on gitlab.com with @robotmay_gitlab if the details can be public, or email them to me at rmay@gitlab.com if not :)

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#79

Post by ziml77 »

ing33k wrote: post #60

/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.

Run a private instance? We haven't had trouble with that approach.

Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API

#80

Post by bshimmin »

pbalau wrote: post #66
ing33k wrote: post #60

/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.

We are using bitbucket atm and I can't fathom a reason to move, care to elaborate?

I use GitHub and Bitbucket fairly extensively and I find Bitbucket painfully slow at times (eg. 7.38s to load a page just now with a whopping two open pull requests on it, whilst somehow transferring 8.8MB of crap; the equivalent page on GitHub is about 6 times better on both fronts) and the UI only ever seems to get more clunky. I fear the tight integration with JIRA is slowly infecting it with JIRA-esque problems.
Post reply on HN