SELECT FOR UPDATE query will not return deadlock error if BF aborted
Bug #1187739 reported by
Seppo Jaakola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola | |||
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
| 5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
Bug Description
if SELECT FOR UPDATE... query is aborted due to multi-master conflict, the client will not get get back deadlock error. From client perspective the transaction is successful.
How to reproduce:
mysql-node1> BEGIN;
mysql-node1> SELECT * FROM t WHERE id=1 FOR UPDATE;
mysql-node2> DELETE FROM t WHERE id=1;
mysql-node1> COMMIT;
| Changed in codership-mysql: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| milestone: | none → 5.5.31-23.7.5 |
| Changed in percona-xtradb-cluster: | |
| milestone: | none → 5.5.31-24.8 |
| Changed in percona-xtradb-cluster: | |
| milestone: | 5.5.31-23.7.5 → 5.5.31-25 |
| Changed in codership-mysql: | |
| milestone: | 5.5.31-23.7.5 → 5.5.32-23.7.6 |
| Changed in percona-xtradb-cluster: | |
| milestone: | 5.5.33-23.7.6 → future-5.5 |
| Changed in codership-mysql: | |
| milestone: | 5.5.33-23.7.6 → 5.5.34-24.9 |
| Changed in codership-mysql: | |
| assignee: | Seppo Jaakola (seppo-jaakola) → nobody |
| assignee: | nobody → Vladislav Klyachin (klyachin) |
| Changed in codership-mysql: | |
| assignee: | Vladislav Klyachin (klyachin) → Seppo Jaakola (seppo-jaakola) |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
| Changed in codership-mysql: | |
| status: | New → In Progress |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #2 |
| Changed in codership-mysql: | |
| status: | In Progress → Fix Committed |
| Changed in codership-mysql: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
SELECT FOR UPDATE... test is passing for current wsrep-5.6 (revision #4012)