Re:Jetpants: a MySQL toolkit for managing billions of rows a...
by Andys on Friday June 08, 2012 @02:47AM
(#4083060)
I got the impression because I didn't see any discussion about the handling of bringing new slaves online (other than how to make it fast). Do you pause one of the slaves to get a consistent dump?
Re:Jetpants: a MySQL toolkit for managing billions of rows a...
by evanelias on Friday June 08, 2012 @09:26AM
(#4084036)
Slave cloning is performed by shutting down mysqld on a standby slave and copying its raw data files. There's no dump involved. This is widely regarded to be the fastest possible way to clone a slave in MySQL.
This is explained in the deeper doc files -- didn't want to bog down the top-level README with implementation details.
Meanwhile, data exporting (for shard splits or table defragmentation) is done on a standby slave with replication stopped.
Definitely please let me know how you got that impression though -- I'm happy to improve confusing things in the docs.
As for ACID compliance: Jetpants is a toolkit for MySQL / InnoDB, and doesn't really impact the referential integrity guarantees of those systems any more or less than other partitioning schemes. MySQL is inherently not a distributed system, for better or worse.