It was MySQL, with the resource contention, in the database cluster
Has someone released a modern version of Cludo?
Code shack GitHub is offering an explanation for a succession of lengthy outages this month - it's the fault of resource contention issues in its primary database cluster during peak loads but more investigation is needed. It's fair to say last week was not a fun time for either GitHub or its users. The service was unavailable …
"It's fair to say last week was not a fun time for either GitHub or its users"
The whole point of Git is it is decentralised. We didn't even notice.
I assume that if it halted your workflow, you really must be using Git incorrectly. Perhaps try to reduce your overconsuming of GitHub specific features?
This post has been deleted by its author
a lot do have this issue, not many companies are public about what causes their outages. DB contention is a pretty common issue in my experience over the past 18 years of dealing with databases in high load(relative to what the app is tested for) environments. I've seen it on MySQL, MSSQL and Oracle, in all cases I've been involved with,the fault was with the app design rather than the DB itself(which was just doing what it was told to do). (side note: I am not a DBA but I play that role on rare occasions).
I remember in one case on MSSQL the "workaround" was to restart the DB and see if the locking cleared, if not restart again, and again, sometimes 10+ times before things were ok again for a while. Fortunately that wasn't an OLTP database. Most critical Oracle DB contentions involved massive downtime due to that being our primary OLTP DB. MySQL contentions mainly just limited the number of transactions the app could do, adding more app servers, more cpu more whatever had no effect(if anything could make the issue worse) the row lock times were hogging up everything.
Git kinda does that for you.
I doubt anyone was unable to code. Github wobbles prevent publishing code to Github only, setting up a new remote is trivial if you prefer to manage it over Github, even in the short term.
You may be locked into Github's non git features of course.
Github and gitlab are convenient (when they work) and both better than average in terms of avoiding lockin, due to the nature of git.
Biting the hand that feeds IT © 1998–2022