statement rollback issue after 5.1.43 merge
Bug #533467 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Critical
|
Seppo Jaakola |
Bug Description
After the 5.1.43, sysbench oltp gives consistency failures with following configuration:
# load balancer choice
load_balancer=
# gcs backend choice
gcs=gcomm
# sysbench configuration
user=root
password=rootpass
host=127.0.0.1
port=3306
users=6
duration=60
requests=0
rows=200
mode=complex
readonly=off
this tetst results in inconsistency in 3 node cluster
Changed in codership-mysql: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
importance: | High → Critical |
milestone: | none → 0.7.3 |
Changed in codership-mysql: | |
status: | In Progress → Fix Committed |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This problme is dues to statement rollbacks, which are not properly handled in wsrep code. post_rollback( ) for both full and stmt rollbacks. However, in stmt rollback case the underlying transaction remains healthy and will commit later. And if post_rollback() was called, the trx has been erased from provider library and wsrep->pre_commit() does not replicate the transaction.
wsrep patch calls wsrep->