# \[innobackupex\] WSREP detected deadlock/conflict and aborted the transaction.

**URL:** <https://forums.percona.com/t/innobackupex-wsrep-detected-deadlock-conflict-and-aborted-the-transaction/6724>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [December 5, 2018, 7:26am UTC](https://forums.percona.com/t/innobackupex-wsrep-detected-deadlock-conflict-and-aborted-the-transaction/6724 "2018-12-05T07:26:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zsebacsi](https://avatars.discourse-cdn.com/v4/letter/z/a5b964/32.png) [@zsebacsi](https://forums.percona.com/u/zsebacsi)\
**Post date:** [December 5, 2018, 7:26am UTC](https://forums.percona.com/t/innobackupex-wsrep-detected-deadlock-conflict-and-aborted-the-transaction/6724/1 "2018-12-05T07:26:51Z")

</div>

hi  
I’m trying to implement a backup solution with innobackupex (we would like to create incremental backups). We have a 3 node galera PXC on mysql 5.7  
I’m using a publicly available simple backup script - can’t find the URL right now - which utilizes innobackupex to create the backups

It’s a production environment with around 1TB data and lots of schemas in it.  
I used lock-ddl-per-table option, because lock-ddl was stopping the whole system, now I get this error after a few hours:

Error: failed to execute query SELECT NAME FROM INFORMATION\_SCHEMA.INNODB\_SYS\_TABLES WHERE SPACE = 47098: WSREP detected deadlock/conflict and aborted the transaction. Try restarting the transaction

tried to google, no luck.

any suggestions where should I start?

T.

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [December 6, 2018, 9:16am UTC](https://forums.percona.com/t/innobackupex-wsrep-detected-deadlock-conflict-and-aborted-the-transaction/6724/2 "2018-12-06T09:16:55Z")

</div>

Hi,  
Are any of your big tables partitioned? If so, you may be hitting: [url][[PXB-1698] Percona Xtrabackup scanning all rows of partitioned tables when using --lock-ddl-per-table - Percona JIRA](https://jira.percona.com/browse/PXB-1698%5B/url%5D) and in such case, --lock-ddl-per-table is just unsafe till the bug will be fixed.