←back to thread

Upgrading Uber's MySQL Fleet

(www.uber.com)
234 points benocodes | 1 comments | 14 Oct 24 12:08 UTC | HN request time: 0.001s | source
Show context
donatj ◴[14 Oct 24 14:16 UTC] No.41837760[source]▶
Interestingly we just went through basically the same upgrade just a couple days ago for similar reasons. We run Amazon Aurora MySQL and Amazon is finally forcing us to upgrade to 8.0.

We ended up spinning up a secondary fleet and bin log replicating from our 5.7 master to the to-be 8.0 master until everything made the switch over.

I was frankly surprised it worked, but it did. It went really smoothly.

replies(1): >>41838123 #
takeda ◴[14 Oct 24 14:56 UTC] No.41838123[source]▶
AFAIK the 8.0 release is one where Oracle breaks compatibility. So anyone considering MariaDB needs to switch before going to 8.0, otherwise switching will be much more painful.
replies(1): >>41844460 #
paulryanrogers ◴[15 Oct 24 02:50 UTC] No.41844460[source]▶
IIRC it wasn't a big break from 5.7 unless you used some odd grouping or relied on its old+lossy defaults.

Though the single threaded performance fell off a cliff, tanking my CI performance.

Maria DB evolved very differently. I'm not sure how they stack up performance wise.

replies(1): >>41848754 #
1. donatj ◴[15 Oct 24 14:06 UTC] No.41848754[source]▶
You can re-enable the old group by behavior, which we did.