EmergencyEMERGENCY? Get 24/7 Help Now!

Percona Server 5.6.14 with TokuDB 7.1 Experimental build

Posted on:



Share Button

We just announced Percona Server 5.6.14 release, and I decided to make this build with the TokuDB 7.1 engine.
The build is available here in the TESTING area.

You are welcome to play with these binaries, but keep in mind:

  • This is an experimental build and not supposed to be used in production environment
  • The binaries built on Ubuntu 12.04 LTS server and may not work on other Linux distributions
Share Button

Vadim Tkachenko

Vadim leads Percona's development group, which produces the Percona Server, Percona Server for MongoDB, Percona XtraDB Cluster and Percona XtraBackup. He is an expert in solid-state storage, and has helped many hardware and software providers succeed in the MySQL market.


, , ,

MySQL, Percona Software

  • I’ll try that. I think the last build, I had issues enabling the tokudb engine even with disabling /sys/kernel/mm/redhat_transparent_hugepage/enabled
    I forget the errors.. must have been busy that day.


  • Interesting. I suppose you can’t really release the sourcecode?


  • Nils,

    There is no problem with releasing source code, it is just there is not much to release.
    It is Percona Server (source code available) + TokuDB engine (source code is available from github Tokutek) + patches to MySQL (source code is available from github Tokutek).
    So the work is really to merge it all together and compile.


  • Interesting, so it all applies cleanly to Percona Server as well? Or did they release specific patches?


  • Nils,

    I’ve uploaded source code there

    The source is less problem, but to get proper toolchain to get it compiled is more complicated.
    You need cmake 2.8.12 and gcc/g++ 4.7 to compile it.


  • Shouldn’t be a problem on Ubuntu, there’s a ppa somewhere.


  • Do you have any idea when this will go into the general release? Toku is a big part of a customers road map.


  • Brian,

    At this time we can’t do any commitment on delivery time, we are still on the exploratory stage.
    We are going to build several alpha- and beta- packages and it will help us a lot
    if users provide feedback on quality and usability meantime.
    When we are satisfied with quality, we will do the general release, I guess it will take few months to get to that point.


  • I’ve been having some serious issues with replication from Percona 5.5 to this test build

    19942 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave. Error_code: 1594


Leave a Reply

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.

Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.

No, thank you. Please do not ask me again.