Spreading writes to all servers: yes. Conflicting updates: no; this problem happens when doing simple inserts. See http://www.toofishes.net/blog/mysql-deadlock

Spreading writes to all servers: yes. Conflicting updates: no; this problem happens when doing simple inserts. See http://www.toofishes.net/blog/mysql-deadlocking-simple-inserts/ http://www.toofishes.net/blog/mysql-deadlocking-simple-inser... -- that's an old blog post but this still happens with a reasonably late mysql and mariadb. I have no reason to believe that it's not a fundamental design failure. It's of course not a Galera issue per se, but rather a more serious InnoDB issue, but it causes problems very easily when using Galera. Perhaps there's a workaround that I don't know of yet? I'd be happy to hear of it. Perhaps it's a fundamental RDBMS problem that I don't understand yet? I'd be happy to be educated if so. As to your last question, I'd expect the database system to accept all such inserts to all instances since they don't conflict with each other in any way.