Maatkit version 1579 released
This release contains bug fixes and new features. The biggest new feature, in my opinion, is a new sync algorithm for mk-table-sync. Now you can sync any table with an index more efficiently than previously. This is the return of the speed I promised earlier. (Though I haven’t yet benchmarked it; I am very short on time these days. Your benchmarks and other contributions are welcome).
I’m finally feeling like the table sync tool is getting in good shape!
Let me know what you think, and of course, if you have questions or bug reports, please use the Sourceforge forums, bug tracker, etc so others can benefit too.
Changelog for mk-heartbeat: 2007-12-27: version 1.0.5 * Added --stop, --sentinel, and --quiet options. * Added --replace option. Changelog for mk-parallel-dump: 2007-12-27: version 1.0.3 * Views with functions caused a crash (bug #1850998, MySQL bug #29408). * --ignoreengine was ignored (bug #1851461). Changelog for mk-table-checksum: 2007-12-27: version 1.1.23 * Updated documentation about version compatibility. * Updated documentation for --replcheck. Changelog for mk-table-sync: 2007-12-27: version 1.0.2 * Syncing via replication did not use REPLACE on the master. * --transaction disabled waiting for a slave to catch up. * Allow one DSN without --replicate, as long as --synctomaster is given. * Added the Nibble sync algorithm. * MASTER_POS_WAIT() failed when the server was not a master (bug #1855480). * DBD::mysql died after 'commands out of sync' error (bug #1856046).
So, just out of curiosity (okay, okay, and because I need it, too) would it be possible/sensical to add some flavor of –no-delete option or the like to stop the archiver tool from deleting rows from the source table?
I have an archive server set up, and I want to have up-to-the-minute data on it, but I want that data also available on the primary server, which will delete older data periodically on its own. So the archiver tool seems to be able to do exactly what I want (I can already limit it to just new rows by using a WHERE clause), but the delete bit is problematic.
(And it doesn’t seem like you can stop it from doing the delete with just a plugin, either)
Thoughts?
J.G.
2 Jan 08 at 4:49 pm
You’re right, there’s no way to prevent the deletes.
I can think of only one possibly bad consequence of allowing this. That is with the –no-ascend option, which might get into an infinite loop. That’s easy to solve: just make –no-delete and –no-ascend mutually exclusive.
Please enter this as a feature request in the Sourceforge bug tracker. I’m going to need to get into this code pretty soon for my own purposes: to allow bulk inserts and deletes. I’ll probably go ahead and add this feature too at the same time.
Xaprb
2 Jan 08 at 5:05 pm