Now i'm find and config mariadb galera cluster? But i don't know why mariadb galera cluster only support InnoDB.
Pls advice to fix it.
Thanks alots
There is essentially no reason to support any engine other than InnoDB. You can have MyISAM or MEMORY tables, but not get the synchronized replication to the other nodes.
Only with InnoDB, can the synchronous replication be achieved. I feel certain that MyISAM and MEMORY will never be fully supported. However, other transaction-safe engines (Tokudb?) might some day.
Why do you want some other engine? Perhaps we can help you achieve the real goal by some other means.
Addenda...
Synchronous replication, the way Galera implemented, requires being able to ROLLBACK even at COMMIT. Otherwise, duplicate keys would be an unsolvable problem when allowing writes to all nodes.
An aside... NDB takes a radically different approach -- "eventual consistency", wherein duplicate keys can get into the system, but the user has to provide an algorithm for fixing the mess.
InnoDB on a single machine checks as the statements within the transaction are being performed. Galera does not. It is "optimistic" -- transactions are performed without checking the other nodes until the COMMIT. This provided performance because of only a single roundtrip to each other node. (Hence, "medium sized" transactions are optimal.)
MyISAM has no way to do ROLLBACK; it depends on locking table up front. Locking tables on another node would be very clumsy and inefficient.
Galera can work efficiently even in a WAN -- again because of the single action at COMMIT.