I need some inputs on how to handle this issue on a Percona XtraDB 5.7.18 cluster (2 master + 1 arbitrator). We are trying to copy a table using “INSERT INTO tbname_new SELECT * FROM tbname;”. This has some 20+ Million rows and it keeps erroring out “WSREP detected deadlock/conflict and aborted the…

WSREP detected deadlock/conflict and aborted the transaction

aserdp July 10, 2017, 6:18am 2

Any input on this. I presume copy of table is a normal operation and its failing.

Topic		Replies	Views
Using pt-online-schema-change with percona 5.7 Percona Toolkit	2	1211	November 29, 2017
Random deadlocks in read-only tables in Percona XtraDB Cluster Percona XtraDB Cluster 5.x	1	1020	May 9, 2017
Deadlock found when trying to get lock; try restarting transaction? Percona XtraDB Cluster 8.x	1	1531	December 18, 2020
'WSREP detected deadlock/conflict and aborted the transaction' on isolated table Percona XtraDB Cluster 5.x mysql , percona	3	7184	July 20, 2021
[innobackupex] WSREP detected deadlock/conflict and aborted the transaction. Percona XtraDB Cluster 5.x	1	4125	December 6, 2018