Lock table not pruned

Bug #1126868 reported by Peter Beaman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Akiban Persistit
High
Peter Beaman

Bug Description

Akiban Server fails DataLoadingTest due to a full temporary volume. This is likely due to an accumulation of lock table records which should be pruned after transactions commit.

Related branches

Revision history for this message
Peter Beaman (pbeaman) wrote :

The recently added Exchange#lock method has a flaw that was exploited by Akiban Server Data Loading Test. It is possible for transactions inserting locks with sequentially varying keys to accumulate in the lock volume in such a way that pruning can't keep up. The result is that the lock volume, which is intended to be a very small in-memory structure, instead exceeds 2GB in size. To fix this will require some additional logic in the pruning code.

Changed in akiban-persistit:
importance: Undecided → High
assignee: nobody → Peter Beaman (pbeaman)
information type: Proprietary → Public
Peter Beaman (pbeaman)
Changed in akiban-persistit:
status: New → Fix Committed
Changed in akiban-persistit:
milestone: none → 3.2.6
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