←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
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 #
hu3 ◴[14 Oct 24 12:50 UTC] No.41837038[source]▶
The upgrade initiative started somewhere in 2023 according to the article.

MySQL 8.4 was released in April 30, 2024.

Their criteria for a "battle tested" MySQL version is probably much more rigorous than the average CRUD shop.

replies(1): >>41837173 #
paulryanrogers ◴[14 Oct 24 13:09 UTC] No.41837173[source]▶
Considering several versions of 8.0 had a crashing bug if you renamed a table, waiting is probably the right choice.
replies(1): >>41838032 #
blindriver ◴[14 Oct 24 14:45 UTC] No.41838032[source]▶
You’re not renaming tables when you’re at scale.
replies(1): >>41838215 #
abhorrence ◴[14 Oct 24 15:04 UTC] No.41838215[source]▶
Sure you do! It's how online schema changes tend to be done, e.g. https://docs.percona.com/percona-toolkit/pt-online-schema-ch... describes doing an atomic rename as the last step.
replies(1): >>41839727 #
yen223 ◴[14 Oct 24 17:29 UTC] No.41839727[source]▶
You aren't renaming tables at scale because there are 27 downstream services that will break if you even think about fixing the name of the revnue_dolars table, and it's not in anyone's OKR to fix it
replies(2): >>41840728 #>>41842030 #
1. sroussey ◴[14 Oct 24 19:02 UTC] No.41840728[source]▶
I’m not sure if this is a joke (ref to OKR was funny, for example), or just naive and not understanding the parent comment. I found it funny either way though.