←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.204s | source
Show context
tiffanyh ◴[14 Oct 24 12:36 UTC] No.41836942[source]▶
Why upgrade to v8.0 (old LTS) and not v8.4 (current LTS)?

Especially given that end-of-support is only 18-months from now (April 2026) … when end-of-support of v5.7 is what drive them to upgrade in the first place.

https://en.m.wikipedia.org/wiki/MySQL

replies(8): >>41836953 #>>41837025 #>>41837032 #>>41837038 #>>41837071 #>>41837144 #>>41837234 #>>41837295 #
pizza234 ◴[14 Oct 24 12:53 UTC] No.41837071[source]▶
I suppose they opted for a conservative upgrade policy, as v8.4 probably includes all the functional additions/changes of the previous v8.1+ versions, and moving to it would have been a very big step.

MySQL is very unstable software - hopefully this will be past - and it's very reasonable to go for the smallest upgrade steps possible.

replies(1): >>41839526 #
hu3 ◴[14 Oct 24 17:09 UTC] No.41839526[source]▶
> MySQL is very unstable software

I've worked on 20+ projects using MySQL in consulting career. Not once stability was a concern. Banking clients would even routinely shut down radom MySQL nodes in production to ensure things continued running smoothly.

As I'm sure users like Uber and Youtube would agree. And these too: https://mysql.com/customers

Unless you know something we don't and we're just lucky.

replies(2): >>41844474 #>>41879132 #
1. paulryanrogers ◴[15 Oct 24 02:54 UTC] No.41844474[source]▶
Depends on your use case. I had a huge table get corrupted after a drop-swap rename during some DDL. 8.0.14 was the version, IIRC.

For simple use cases or with tried and true patch sets I'm sure it can be a work horse.