Comments - Understanding replication and read lock contention problems
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Thanks so much for your help and explanation.
Perhaps the solution for me right now is to configure all clients to read from their local copy and to write any changes directly to the primary? Would this avoid the deadlock issue?
With galera, there is no primary. Updates to the local node are replicated to other members of the cluster. It won't necessary avoid deadlock. The deadlocks shows are count updates and I can't see the order that spam assassin is doing database updates. With an understanding of that you might be able to do a small code change to avoid it, or at least handle the deadlock (retry maybe).