Percona MyRocks存储引擎和复制
[英]Percona MyRocks storage engine and replication
问题描述
Can anyone advise me if we choose Percona MyRocks storage engine on the slave and replicating off Galera Cluster running Innodb engine. 
如果我们在从服务器上选择Percona MyRocks存储引擎并复制运行Innodb引擎的Galera Cluster，谁能告诉我。 Would such replication work and if so what are the chances of it breaking on schema changes done on Galera cluster via Pt-schema-change. 这样的复制是否可以工作，如果可以，那么通过Pt-schema-change在Galera集群上完成的架构更改将有可能中断。
1 个解决方案
解决方案1
1 2017-10-02 23:43:48
InnoDB is the only supported storage engine for Galera/PXC replication. InnoDB是Galera / PXC复制唯一受支持的存储引擎。
Re-reading your question, it seems you want to use MyRocks on a slave in a 'traditional' async replication scenario, not as part of a cluster. 重新阅读您的问题，似乎您想在“传统”异步复制方案中的从属服务器上使用MyRocks，而不是作为集群的一部分。 This should work fine as long as that slave does not participate in the Galera cluster. 只要该从属服务器不参与Galera群集，此方法就可以正常工作。 MyRocks only really works well with ROW format, so no STMT/MIX. MyRocks仅在ROW格式下才能很好地工作，因此没有STMT / MIX。 Any replicated DDL that might alter the engine will cause the slave table alteration to the target engine. 任何可能更改引擎的复制DDL都会导致从表更改为目标引擎。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.