Buy Percona ServicesBuy Now!

WSREP detected deadlock/conflict and aborted the transaction

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • WSREP detected deadlock/conflict and aborted the transaction

    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 transaction."

    We tried even splitting it into smaller chunks of 200k rows and still it gets that error. Please note we are writing only to one node.

    Any input on this is highly appreciate

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

    Comment


    • #3
      "WSREP detected deadlock/conflict and aborted the transaction." ... unfortunately is generic error.

      Can you share error log ?

      Comment


      • #4
        Hi,

        I believe this is the same issue reported in PT-229: https://jira.percona.com/browse/PT-229.
        You can download the latest version from here: https://github.com/percona/percona-t...-schema-change

        Regards.

        Comment

        Working...
        X