Deadlock while running ineffective UPDATE query on 5.5.33 with STATEMENT-based binlog format
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
New
|
Undecided
|
Unassigned | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After upgrading cluster nodes to 5.33 we are faced with following issue.
Running this query:
update users set user_agent=
Yields:
ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
The error is produced if fields are the same as already committed to database (i.e. running query several times in a row).
If you run the query with different values than those already in the table, the query is successful.
If you run the query again with same values again, the above error is produced every time on every node.
Note that we have single node for read/write over HAProxy, and others are for backup/standby purposes.
We had no issues with this on 5.30. or any other previos versions of MySQL/Percona server (from Mysql 4.x, 5.x, Percona Server 5.5 to XtraDB cluster 5.30).
For testing purposes, I have lowered wsrep_slave_threads to 1, but it didn't help.
I have also tried testing other tables and other databases and updating other kinds of fields (int, varchar, etc) but the problem is persists.
All afflicted databases are INNODB.
summary: |
- Deadlock while running ineffective UPDATE query on 5.33 + Deadlock while running ineffective UPDATE query on 5.5.33 with + STATEMENT-based binlog format |
Changed in percona-xtradb-cluster: | |
status: | Invalid → In Progress |
status: | In Progress → Invalid |
And let me guess, your effective binlog_format is STATEMENT?