Percona Server 5.6.14 with TokuDB 7.1 Experimental build

PREVIOUS POST
NEXT POST

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
PREVIOUS POST
NEXT POST

Comments

  1. says

    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.

  2. says

    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.

  3. Nils says

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

  4. says

    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.

  5. paul says

    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

Your email address will not be published. Required fields are marked *