Locally, in one node, transaction isolation works as with native
InnoDB, so all levels can be used.
But cluster wide, between transactions processing in separate nodes,
Galera implements transaction level called "SNAPSHOT ISOLATION". The
SNAPSHOT ISOLATION level is between REPEATABLE READ and SERIALIZABLE
levels.
SERIALIZABLE level cannot be guaranteed in multi-master use case,
because Galera replication does not carry transaction read set. Also,
SERIALIZABLE transaction is vulnerable for multi-master conflicts. It
holds read locks and any replicated write to read locked row will
cause transaction abort. So you better not use it in Galera Cluster.
-seppo