Project

General

Profile

Feature #121

Abort idle transactions on timeout

Added by ronald - about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Mulgara
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

If a client goes away while holding the write lock, the write lock is
never released, leading to mulgara being locked forever. Currently the
timeout "only" sets the timeout on the internal transaction manager
which just causes the transaction to be marked for rollback on a
timeout. However, setting the timeout should also start a timer which
is used to abort a non-active transaction (this should happened for
both read-write as well as read-only transactions as the latter could
be holding on to a phase, leading to a "memory leak").

#1

Updated by Andrae Muys - about 14 years ago

  • Status changed from New to In Progress
#2

Updated by ronald - about 14 years ago

  • Status changed from In Progress to Closed
  • Resolution set to fixed

(In r1098) Merged branch mgr-121-lockrecovery.

This contains three sets of changes:
1. support for idle and transaction timeouts - this closes #121, #122, and #125.
2. synchronization fixes and simplifications for the transactions
3. miscellaneous small fixes to the transactions - this closes #101.

Also available in: Atom PDF