←back to thread

Upgrading Uber's MySQL Fleet

(www.uber.com)
234 points benocodes | 6 comments | 14 Oct 24 12:08 UTC | HN request time: 0.422s | source | bottom
1. jeffbee ◴[14 Oct 24 15:11 UTC] No.41838276[source]▶
File under "things you will never need to do if you use cloud services".
replies(3): >>41838301 #>>41838456 #>>41839316 #
2. martinsnow ◴[14 Oct 24 15:14 UTC] No.41838301[source]▶
Nah random outages because the RDS instance you were on decided to faceplant itself, or the weird memory to bandwidth scaling AWS has chosen will make you pull your hair out on a high traffic day.

It's just different problems.

replies(1): >>41838385 #
3. jeffbee ◴[14 Oct 24 15:23 UTC] No.41838385[source]▶
The company in the article is doing < 200qps per node. Unless they are returning a feature-length video file from every query, they are nowhere near any hardware resource limits.
4. paxys ◴[14 Oct 24 15:31 UTC] No.41838456[source]▶
At Uber's scale they are a cloud service.
5. mannyv ◴[14 Oct 24 16:51 UTC] No.41839316[source]▶
That's not true. The RDS 5.7 instances are EOL so you have to upgrade them at some point.

At least in RDS, that will be a one-way upgrade ie: no rollback will be possible. That said, you can upgrade one instance at a time in your cluster for a no-downtime rollout.

replies(1): >>41839428 #
6. jeffbee ◴[14 Oct 24 17:00 UTC] No.41839428[source]▶
Hosted MySQL is not what I meant. That just means you're paying more to have all the same problems. The kind of cloud service I am alluding to is cloud spanner, cloud bigtable, dynamodb.