More Thoughts on Constituent Replicator
Oddly enough the announcement of the constituent replicator coincides with some MySQL replication problems we’ve been feeling over the last couple of weeks.
… so here are some more thoughts and feature suggestions:
– get this in Drizzle. From what I understand they ripped out replication since the code wasn’t as elegant as the Drizzle core. I’ve heard this echoed by a number of developers so this seems like a good decision.
– Add the ability to promote a slave to a master and re-parent existing slaves to the new master – easily. I think one can do this now with log_slave_updates but it needs to be easier to setup.
– Per-statement synchronous replication support.
This could be done by a comment or an extension to the MySQL. For example:
INSERT /* replsync */ INTO FOO ...
The vast majority of my code can be asynchronous but occasionally I have to have a synchronous code block. We’ve written some code to do this ourselves but it would be nice if it were in the SQL layer.
Also, focus on getting a 1.0 release out soon. The key features we need are:
– Parallel update on slaves to increase performance
– Checksums on replication events
– Table consistency check