Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Upgrading Uber's MySQL Fleet

uber.com

Post reply on HN
Print view View original

21–30 of 215 posts

Re: Upgrading Uber's MySQL Fleet

#21

Post by paulryanrogers »

hu3 wrote: post #12
tiffanyh wrote: post #2

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

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.

Considering several versions of 8.0 had a crashing bug if you renamed a table, waiting is probably the right choice.

Re: Upgrading Uber's MySQL Fleet

#22

Post by anonzzzies »

hu3 wrote: post #13
whalesalad wrote: post #4

So satisfying to do a huge upgrade like this and then see the actual proof in the pudding with all the reduced latencies and query times.

Yeah some numbers caught my attention like ~94% reduction in overall database lock time. And to think they never have to worry about VACUUM. Ahh the peace.

Yeah, until vacuum is gone, i'm not touching postgres. So many bad experiences with our use cases over the decades. I guess most people don't have our uses, but i'm thinking Uber does.

Re: Upgrading Uber's MySQL Fleet

#23

Post by PedroBatista »

tiffanyh wrote: post #2

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

MySQL 8 and beyond has been riddled with bugs and performance regressions. It was a huge rewrite from 5.7.

8 has nice features and I think they evaluated it as stable enough to upgrade their whole fleet to it. I'm pretty sure from 8 to 8.4 the upgrades will be much simpler.

Re: Upgrading Uber's MySQL Fleet

#24

Post by paradite »

I can tell from a mile away that this is written by ChatGPT / Claude, at least partially.

"This distinction played a crucial role in our upgrade planning and execution strategy."

"Navigating Challenges in the MySQL Upgrade Journey"

"Finally, minimizing manual intervention during the upgrade process was crucial."

Re: Upgrading Uber's MySQL Fleet

#26

Post by BarryMilo »

kavunr wrote: post #19
indulona wrote: post #17

[flagged]

I had a similar reaction when reading https://engineeringblog.yelp.com/2024/10/migrating-from-post...

I get the urge to standardize infrastructure but... wow. After reading the whole thing, I get why they thought it was worth doing, but you'd think they'd just hire a Postgres guy or two. Especially when they looked at the missing features, this feels like a downgrade...

Re: Upgrading Uber's MySQL Fleet

#27

Post by notinmykernel »

paradite wrote: post #24

I can tell from a mile away that this is written by ChatGPT / Claude, at least partially. "This distinction played a crucial role in our upgrade planning and execution strategy." "Navigating Challenges in the MySQL Upgrade Journey" "Finally, minimizing manual intervention during the upgrade process was crucial."

Agree. Repetition (e.g., crucial) in ChatGPT is an issue.

Re: Upgrading Uber's MySQL Fleet

#28

Post by cbartholomew »

tiffanyh wrote: post #2

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

They started in 2023. v8.0 was the current LTS when they started.

Re: Upgrading Uber's MySQL Fleet

#29

Post by brunocvcunha »

paradite wrote: post #24

I can tell from a mile away that this is written by ChatGPT / Claude, at least partially. "This distinction played a crucial role in our upgrade planning and execution strategy." "Navigating Challenges in the MySQL Upgrade Journey" "Finally, minimizing manual intervention during the upgrade process was crucial."

I can tell just by the frequency of the word “delve”
Post reply on HN