# Slave replication when using both TokuDB and InnoDB engines - any caveats?

**URL:** <https://forums.percona.com/t/slave-replication-when-using-both-tokudb-and-innodb-engines-any-caveats/6670>\
**Category:** Percona Server for MySQL 5.7\
**Created:** [November 7, 2018, 3:23am UTC](https://forums.percona.com/t/slave-replication-when-using-both-tokudb-and-innodb-engines-any-caveats/6670 "2018-11-07T03:23:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lkuchars](https://avatars.discourse-cdn.com/v4/letter/l/85e7bf/32.png) [@lkuchars](https://forums.percona.com/u/lkuchars)\
**Post date:** [November 7, 2018, 3:23am UTC](https://forums.percona.com/t/slave-replication-when-using-both-tokudb-and-innodb-engines-any-caveats/6670/1 "2018-11-07T03:23:57Z")

</div>

Hi there. For last few days I was experimenting with TokuDB engine. Compression ratios are impressive for some of our tables. I’d like to ask experts if there are any issues when I setup such ‘double engine’ percona server as Master and try to replicate it to another node (slave).

Are TokuDB tables replicated too? Has this been done by anybody on production systems before?