> In practice, you should typically only send write traffic to 1 galera node Yes, we did that too, it's the only way to reduce the deadlock and certification f

> In practice, you should typically only send write traffic to 1 galera node Yes, we did that too, it's the only way to reduce the deadlock and certification failure with Galera. However, it won't prevent a single `ALTER TABLE` to lock up the entire cluster. You can use `pt-online-schema-change` to workaround that, but it's not perfect. We've switched to simple Asynchronous Replication with Openark Orchestrator for the majority of our clusters and the DBA team is much happier now.