Incident with Issues and Pull Requests

Re:Incident with Issues and Pull Requests by tonyhb on Thursday May 11, 2023 @10:27AM (#35902591)

Ah, unbalanced shards via wrong sharding keys was an issue at one point, IIRC. I remember talking with an SRE there when something bad happened at GitHub last year, and I know that this time the current DB cluster failed.

To be clear, I _was_ mapping previous incidents with this year's incident — no competitor or hard feelings involved. I _really_ like Vitess, fwiw.

[ Parent | on HN ]

Re:Incident with Issues and Pull Requests by samlambert on Thursday May 11, 2023 @10:52AM (#35903040)

That wasn't clear.

Side note: "Autosharding" is largely a myth that unproven databases are touting. Sharding is complex and requires planning and control. Databases that start shuffling data round without oversight produce nasty surprises. Trying to be too magic is normally always a mistake with databases.

[ Parent | on HN ]

Re:Incident with Issues and Pull Requests by tonyhb on Thursday May 11, 2023 @11:04AM (#35903229)

Yeah, fair, totally get it. Wasn't aiming to spread FUD, and I know that FDB is a little hard to compare against... it is pretty magic with how it routes and shards :D (https://forums.foundationdb.org/t/keyspace-partitions-perfor...)

[ Parent | on HN ]

Re:Incident with Issues and Pull Requests by tonyhb on Tuesday May 16, 2023 @05:52PM (#35968245)

For posterity: https://github.blog/2023-05-16-addressing-githubs-recent-ava...

It was the DB, and it was rogue usage on May 10, so I'm standing by my original comment

[ Parent | on HN ]