Inconsistent certification index purge

Bug #1099546 reported by Alex Yurchenko on 2013-01-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Alex Yurchenko

Bug Description

It was found that under very heavy CPU contended load with high (25%) deadlock rate certification index may be purged inconsistently, and - worst of all - PREMATURELY, erasing information required for certification of upcoming writesets, which leads to inconsistent certification results and consequent data inconsistency.

Related branches

Alex Yurchenko (ayurchen) wrote :

Fix pushed in r143. Using cert_.get_safe_to_discard_seqno() instead of apply_monitor_.last_left() to broadcast commit cut.

Changed in galera:
status: In Progress → Fix Committed
Alex Yurchenko (ayurchen) wrote :

Fix released by Percona.

Changed in galera:
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