Comment 2 for bug 1080913

Mixing Galera with MyISAM is of-course not part of best-practice but I assume the support is left out so that end-user can easily migrate from MyISAM to InnoDB.

Anyway,

I tried the given use-case with latest 5.6 trunk

1. Start node-1,2
2. node-1: create myisam table t1 with auto-inc, insert (NULL)
3. node-2: no table t1 with as wsrep_replicate_myisam is OFF by default.
4. node-1: set wsrep_replicate_myisam = 1. create myisam table t2 (note you can't use t1 it is not replicated)
5. node-1: insert (NULL)
6. node-2: table and insert are visible so replication with auto-inc column succeed.

IMPORTANT: there are lot of other issues with use of MyISAM that original exist in upstream.
(For example: what happen in-case you continue to insert into t1 post replicate_myisam = 1)
node-2: doesn't have the table so node-2 generate error if it get insert stmt on t1 as t1 doesn't exist.
What if I now create t1 (engine=innodb) on node-2 and insert (NULL) on node-1. This passes when it should ideally fail
as both tables are of different engine-type.

There are lot of other such interesting observations and so the support for MyISAM is experimental.

Anyway, the main issue is working with latest 5.6 so I will close this bug.