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.
Nils
12 years ago
Interesting. I suppose you can’t really release the sourcecode?
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.
Nils
12 years ago
Interesting, so it all applies cleanly to Percona Server as well? Or did they release specific patches?
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.
paul
12 years ago
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
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
https://www.percona.com/redir/downloads/TESTING/Percona-TokuDB/percona-server-5.6.14-tokudb-7.1.0.src.tar.gz
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