Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.34-galera
-
None
-
None
Description
Same test as in #5604.
The UPDATE doesn't update anything, but a deadlock is throw on the COMMIT.
[2014-02-03 10:47:24] 12: [WARNING] Updated didn't matched the inserted! Inserted: 5, Updated: 0
|
[2014-02-03 10:47:24] 12: [ERROR 1] UPDATE 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
|
This is great! But wsrep_local_bf_aborts status value doesn't increase.
From the error log:
140202 19:49:23 [Note] WSREP: BF kill (1, seqno: 3311463), victim: (132) trx: 3633573
|
140202 19:49:23 [Note] WSREP: Aborting query: void
|
140202 19:49:23 [Note] WSREP: kill IDLE for 3633573
|
140202 19:49:23 [Note] WSREP: enqueuing trx abort for (132)
|
140202 19:49:23 [Note] WSREP: signaling aborter
|
140202 19:49:23 [Note] WSREP: WSREP rollback thread wakes for signal
|
140202 19:49:23 [Note] WSREP: client rollback due to BF abort for (132), query: (null)
|
140202 19:49:23 [Note] WSREP: WSREP rollbacker aborted thd: (132 140630848161536)
|
140202 19:49:23 [Note] WSREP: Deadlock error for: (null)
|
The timestamp mismatch is between my local computer and my node, sorry.
Attachments
Issue Links
- relates to
-
-
- Closed
-