Percona XtraDB Cluster Limitations¶
The following limitations apply to Percona XtraDB Cluster:
Replication works only with InnoDB storage engine. Any writes to tables of other types, including system (
mysql.*) tables, are not replicated. However,
DDLstatements are replicated in statement level, and changes to
mysql.*tables will get replicated that way. So you can safely issue
CREATE USER..., but issuing
INSERT INTO mysql.user...will not be replicated. You can enable experimental MyISAM replication support using the
UNLOCK TABLESis not supported in multi-master setups
- Lock functions, such as
RELEASE_LOCK(), and so on
Query log cannot be directed to table. If you enable query logging, you must forward the log to a file:
log_output = FILE
general_log_fileto choose query logging and the log file name.
Maximum allowed transaction size is defined by the
LOAD DATA INFILEprocessing will commit every 10 000 rows. So large transactions due to
LOAD DATAwill be split to series of small transactions.
Due to cluster-level optimistic concurrency control, transaction issuing
COMMITmay still be aborted at that stage. There can be two transactions writing to the same rows and committing in separate Percona XtraDB Cluster nodes, and only one of the them can successfully commit. The failing one will be aborted. For cluster-level aborts, Percona XtraDB Cluster gives back deadlock error code:
(Error: 1213 SQLSTATE: 40001 (ER_LOCK_DEADLOCK)).
XA transactions are not supported due to possible rollback on commit.
The write throughput of the whole cluster is limited by the weakest node. If one node becomes slow, the whole cluster slows down. If you have requirements for stable high performance, then it should be supported by corresponding hardware.
The minimal recommended size of cluster is 3 nodes. The 3rd node can be an arbitrator.
InnoDB fake changes feature is not supported.
enforce_storage_engine=InnoDBis not compatible with
binlog_rows_query_log_eventsvariable is not supported.
When running Percona XtraDB Cluster in cluster mode, avoid
ALTER TABLE ... IMPORT/EXPORTworkloads. It can lead to node inconsistency if not executed in sync on all nodes.
All tables must have the primary key. This ensures that the same rows appear in the same order on different nodes. The
DELETEstatement is not supported on tables without a primary key.
- Galera Documentation: Tables without Primary Keys