"1B+ rows in it with mysql?" Been there, really no fun.

midom · on July 26, 2016

As long as you can shard (across multiple instances, or even within same instance, to avoid B-Tree latching), 1B+ rows within MySQL is piece of cake.

Also, MySQL* is getting LSM-Tree support lately, which makes high performance data ingestion combined with OLTP workload quite feasible.

_Codemonkeyism · on July 27, 2016

"I wonder how Uber adds an index to a table that already has 1B+ rows in it with mysql?"

"As long as you can shard "

Not sure how sharding helps with 1B+ tables when adding indices, care to share?

Swannie · on July 28, 2016

This is: "Split the index in your application code."

And then do your joins, in your application code.

fasteo · on July 26, 2016

Percona to the rescue [1]. Works flawlessly, at least in our case.

barrkel · on July 26, 2016

Am there right now, it's not really a problem - you just have to plan your schema changes and use Percona OST.

maximegarcia · on July 26, 2016

Saved my life a few time :)

_Codemonkeyism · on July 27, 2016

Thanks!

Groxx · on Aug 6, 2016

Also been there. Percona Toolkit works fine (though it's not load-aware enough, so we changed the backfill logic).

Plus, in 5.7, there are a fair number of online-DDL changes, and adding indexes is (usually) one of them.