EmergencyEMERGENCY? Get 24/7 Help Now!

Percona Toolkit 1.0.1 released

 | September 7, 2011 |  Posted In: MySQL, Percona Software


Daniel and I and the Percona release engineering team are proud to announce version 1.0.1 of Percona Toolkit. This toolkit is Percona’s suite of DBA and sysadmin productivity tools for MySQL. It is the successor to the popular Maatkit and Aspersa toolkits. Percona Toolkit is available for immediate download at percona.com/downloads/percona-toolkit/.

Helpful links:

Baron Schwartz

Baron is the lead author of High Performance MySQL.
He is a former Percona employee.


  • Looking at the list it appears as though the vast majority, if not all, tools from Maatkit & Aspersa made it through to Percona Toolkit. Is that the case?

    I have a particular interest in pt-online-schema-change: how far has it been used+tested on your customers production servers?

  • Awesome thanks Baron and Daniel.

    Daniel glad to see some form of mysqlreport in form of pt-mysql-summary suggestion from my comment (now gone) from http://www.infoworld.com/d/data-management/10-essential-mysql-tools-admins-168018 made it into Percona Toolkit 🙂

  • Hi Baron

    Could you elaborate on the relationship between this and Aspersa/Maatkit? Earlier you announced percona-toolkit as a fork of the two upstream projects (adding that you were excited about it). From my point of view Maatkit and Aspersa were yours and Daniel’s projects anyway, so at most I see it as a re-branding.

    Or is this a distribution of tools that could potentially include also something else than Aspersa and Maatkit? Does it mean you would work on those projects as upstream and the function of Percona Toolkit is just to provide a selection you recommend in a convenient package? I see you’ve renamed the command line tools, so maybe no?

    If this is a fork, should anyone expect Maatkit and Aspersa to live on a separate life?

  • Baron,

    This is excellent news. Congratulations and many thanks. As we move our installations over to Percona, being confident in our toolset will help us reach our goals. My take on the timeline for Maatkit and Aspersa was that they should work with Percona just like they would the MySQL distribution, however having it served here only adds confidence in our choice MySQL branch.

    Thanks again, the Debian package is particularly appreciated.

  • Thanks for all the comments.

    We will add it to the repositories; I thought it was there already, actually, but I’m not that smart about repositories. I’ll ask the RelEng team to take care of that.

    Most of the Maatkit + Aspersa tools are here, but we omitted ones that were solutions in search of a problem, or turned out not to be a good fit (e.g. mk-loadavg), or ones that aren’t really helpful to us in our work with customers. In our next release we’ll also remove stuff from tools that isn’t relevant. For example, it’s nice that mk-query-digest can parse Postgres log files, but we want to make pt-query-digest simpler, and yanking out that code will help.

    pt-online-schema-change hasn’t been extensively tested in the real world and I am not confident in it myself, because I haven’t used it personally. But it seems important enough that we included it, even though its production/beta/incubation status is a bit gray-zone.

    I don’t intend to do any further upstream work on Maatkit or Aspersa, and I’ve updated their websites to say so. The feature request and bug lists on those tools is just so huge that it’s unmanageable, so I expect that some people will be unhappy that no one is going to fix bugs in features that we’ll remove entirely in the PT tools, for example. But that is life. We can’t focus in two places at once, and this fork-and-go approach is actually trying to solve that problem by providing one clear focus and priority for development.

  • Loving the toolset so far. It’s already been quite helpful to me this week. Great work as usual 🙂 A small thing, but I love that the tools are available at percona.com/get. Huge timesaver when you end up troubleshooting on foreign servers.

  • I’d think you should remove pt-table-checksum *after* it’s obsolete, not before, eh? 🙂 To save other people the trouble, here’s a link directly into the old code base for the file, which worked for what I needed: http://bazaar.launchpad.net/~percona-toolkit-dev/percona-toolkit/1.0/download/71/ptchecksumfilter-20110624220137-or26tn4expb9ul2a-2/pt-checksum-filter

Leave a Reply