I'm pleased to announce a new release of the openark kit. There's a lot of new functionality inside; following is a brief overview.
The openark kit is a set of utilities for MySQL. They solve everyday maintenance tasks, which may be complicated or time consuming to work by hand.
It's been a while since the last announced release. Most of my attention was on mycheckpoint, building new features, writing documentation etc. However my own use of openark kit has only increased in the past few months, and there's new useful solutions to common problems that have been developed.
I've used and improved many tools over this time, but doing the final cut, along with proper documentation, took some time. Anyway, here are the highlights:
New tool: oak-hook-general-log
oak-hook-general-log hooks up a MySQL server and dumps the general log based on filtering rules, applying to query role or execution plan. It is possible to only dump connect/disconnect entries, queries which make a full table scan, or use temporary tables, or scan more than X number of rows, or...
I'll write more on this tool shortly.
New tool: oak-prepare-shutdown
This tool makes for an orderly and faster shutdown by safely stopping replication, and flushing InnoDB pages to disk prior to shutting down (keeping server available for connections even while attempting to flush dirty pages to disk). A typical use case would be:
oak-prepare-shutdown --user=root --ask-pass --socket=/tmp/mysql.sock && /etc/init.d/mysql stop
New tool: oak-repeat query
oak-repeat-query repeats executing a given query until some condition holds. The condition can be:
- Number of given iterations has been reached
- Given time has elapsed
- No rows have been affected by query
The tool comes in handy for cleanup jobs, warming up caches, etc.
New tool: oak-get-slave-lag
This simple tool just returns the number of seconds a slave is behind master. But it also returns with an appropriate exit code, based on a given threshold: 0 when lag is good, 1 (error exit code) when lag is too great or slave fails to replicate.
This tool has been used by 3rd party applications, such as a load balancer, to determine whether a slave should be accessed.
Updated tool: oak-chunk-update
This extremely useful utility breaks down very long queries into smaller chunks. These could be queries which should affect a huge amount of rows, or queries which cannot utilize an index.
Updates to the tool include limiting the range of rows the tool scans, by specifying start and stop position (either by providing constant values or by SELECT query). Also added is auto-termination when no rows are found to be affected. Last, it is possible to override INFORMATION_SCHEMA lookup by explicitly specifying chunking key.
This tool works great for your daily/weekly/monthly batch jobs; in creating DWH tables; populating new columns; purging old entries; clearing data based on non-indexed values; generating summary tables; and more.
Frozen tool: oak-apply-ri
I haven't been using this tool for a while. The main work down by this tool can be done with oak-chunk-update. There are some additional safety checks oak-apply-ri provides; I'm thinking over if they justify the tool's existence.
Frozen tool: oak-online-alter-table
With the appearance of Facebook’s Online Schema Change (OSC) tool, which derives from oak-online-alter-table, I'm not sure I will continue developing the tool. I intend to wait for general feedback on OSC before making a decision.
Documentation is now part of openark kit's SVN repository.
The openark kit project is currently hosted by Google Code. Downloads are available at the Google Code openark kit project page.
Downloads are available in the following packaging formats:
- .deb package, to be installed on debian, ubuntu and otherwise debian based distributions.
- .rpm package, architecture free (noarch), for RPM supporting Linux distributions such as RedHat, Fedora, CentOS etc.
- .tar.gz using python's distutils installer.
- source, directly retrieved from SVN or from above python package.
- Some distribution specific RPM packages, courtesy Lenz Grimmer.
Your feedback is welcome! I may not always respond promptly; and I confess that some bugs were left open for more than I would have liked them to. I hope to make for good quality of code, and bug reporting is one major factor you can control.