We have a daisy-chain replication with 3 masters. Since the upgrade from 10.1 to 10.2.9 we get deadlocks 1-2 times a week on one specific table (varies from 0 to 500 entries) which is written by the local server and also by the replication. The replication stucks at the state "Unlocking tables" and stops the whole replication. It is not possible to kill the process within MariaDB, you have to kill the whole mysql-process with kill -9.
There are no errors in error-log. A recent upgrade from 10.2.9 to 10.2.10 did not solve the problem. Any ideas?
• Stucked Process
• Workaround at Deadlock