Fatal return code from wsrep provider is ignored in two instances

Bug #736977 reported by Alex Yurchenko on 2011-03-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Alex Yurchenko

Bug Description

Here we have two instances where fatal error is ignored - which leads to node stall and blocking of a whole cluster.
110313 19:34:53 [ERROR] WSREP: invalid state APPLYING (FATAL)
  at galera/src/replicator_smm.cpp:abort_trx():679
110313 19:34:53 [Warning] WSREP: cancel commit bad exit: 6 9470094
110313 19:44:32 [ERROR] Slave SQL: Could not execute Update_rows event on table test.comm04; Deadlock found when trying to get lock; try restarting transaction, Error_code: 1213; handler error HA_ERR_LOCK_DEADLOCK; the event's master log FIRST, end_log_pos 8700, Error_code: 1213
110313 19:44:32 [Warning] WSREP: RBR event 30 apply warning: 149, 6393734
110313 19:44:32 [Warning] WSREP trx_replay failed for: 7

Changed in codership-mysql:
assignee: nobody → Alex Yurchenko (ayurchen)
importance: Undecided → High
milestone: none → 0.7
status: New → Confirmed
Changed in codership-mysql:
status: Confirmed → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers