Managing large sharded MySQL topologies with Jetpants - Percona

More documents

Recommendations

Info

3 magic bullets of data migration Useful background for shard splits, pool merges, initial sharding, major schema changes 1. Redundant writes 2. Move reads separately, before stopping redundant writes 3. Chose a cutover ID “in the future” Managing large sharded topologies with Jetpants
Redundant writes • Make your app write data to an old source and a new source, until the migration is finished • The writes to the new source are "dark writes" until migration completes — nothing reads from them yet • If you're not making schema changes, you can leverage MySQL replication for this in interesting ways • Otherwise, you can do the redundant writes at the app or service level Managing large sharded topologies with Jetpants
Page 1 and 2: Managing Large Sharded Topologies w
Page 3 and 4: Motivations for Jetpants 1. Split r
Page 5 and 6: Shard split automation prereqs •
Page 7 and 8: Tumblr’s Scale, Oct 2012 • 103
Page 9 and 10: This means three things 1. We're hi
Page 11 and 12: Implementation • Ruby objects rep
Page 13 and 14: How Jetpants exports data • Creat
Page 15: Import/export use cases • Defragm
Page 19 and 20: Future Cutover • Always deploy cu
Page 21 and 22: Standby Slave, Standby Slave, blogs
Page 29 and 30: Why this matters "Resharding - I do
Page 31 and 32: Merging pools How to merge pool A i
Page 33 and 34: Map/Reduce in MySQL? Not exactly, b
Page 35 and 36: Plugin system • Built using Ruby
Page 37 and 38: Plugins: asset tracker • Jetpants
Page 39 and 40: Jetpants Roadmap • Nonstandard po

Managing large sharded MySQL topologies with Jetpants - Percona

Create successful ePaper yourself

Delete template?

Save as template?