Support for tokudb, master-slave

Bug #1299430 reported by Seppo Jaakola on 2014-03-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Seppo Jaakola
Percona XtraDB Cluster moved to
Status tracked in 5.6

Bug Description

It looks like supporting tokudb storage engine in master-slave model is a low hanging fruit. What needs to done is:

1. populate key information from tokudb handlerton (write_row, delete_row, update_row methods)
2. Find out unique tokudb transaction ID and introduce transaction to wsrep provider
3. make sure wsrep handlerton accepts both innodb and tokudb transactions

With that, tokudb transactions should replicate to cluster. Parallel applying may not work out of the box, as tokudb may have other transaction dependencies than plain key values.

Multi-master replication is much harder to reach, and involves implementing prioritized transactions for toku engine.

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Wishlist
assignee: nobody → Seppo Jaakola (seppo-jaakola)
Seppo Jaakola (seppo-jaakola) wrote :

yes, yes, Oracle's mysql branch does not have tokudb storage engine. So, I pushed this work into mariadb-galera-10 (MGC10) repository. Merges to PXC can be picked from there. Here's the first revision:

I was able to run sysbench OLTP with this build, and using single applier.

Makes sense for PXC wishlist for sure...

Changed in codership-mysql:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers