Support for tokudb, master-slave
Bug #1299430 reported by
Seppo Jaakola
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
Wishlist
|
Seppo Jaakola | |||
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.5 |
Confirmed
|
Wishlist
|
Unassigned | |||
| 5.6 |
Confirmed
|
Wishlist
|
Unassigned | |||
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) |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
Revision history for this message
| Valerii Kravchuk (valerii-kravchuk) wrote | #2 |
| Changed in codership-mysql: | |
| status: | In Progress → Fix Committed |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
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:
http://
I was able to run sysbench OLTP with this build, and using single applier.