ref/lock/dead.html

<!--$Id: dead.so,v 10.21 2005/12/02 17:27:50 alanb Exp $-->
<!--Copyright (c) 1997,2008 Oracle.  All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<html>
<head>
<title>Berkeley DB Reference Guide: Deadlock detection</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"><!--meow--></a>
<table width="100%"><tr valign=top>
<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Locking Subsystem</dl></b></td>
<td align=right><a href="../lock/stdmode.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/timeout.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p align=center><b>Deadlock detection</b></p>
<p>Practically any application that uses locking may deadlock.  The
exceptions to this rule are when all the threads of control accessing
the database are read-only or when the Berkeley DB Concurrent Data Store product is used; the
Berkeley DB Concurrent Data Store product guarantees deadlock-free operation at the expense of
reduced concurrency.  While there are data access patterns that are
deadlock free (for example, an application doing nothing but overwriting
fixed-length records in an already existing database), they are
extremely rare.</p>
<p>When a deadlock exists in the system, all the threads of control
involved in the deadlock are, by definition, waiting on a lock.  The
deadlock detector examines the state of the lock manager and identifies
a deadlock, and selects one of the lock requests to reject.  (See
<a href="../../ref/lock/config.html">Configuring locking</a> for a
discussion of how a participant is selected).  The <a href="../../api_c/lock_get.html">DB_ENV-&gt;lock_get</a> or
<a href="../../api_c/lock_vec.html">DB_ENV-&gt;lock_vec</a> call for which the selected participant is waiting then
returns a <a href="../../ref/program/errorret.html#DB_LOCK_DEADLOCK">DB_LOCK_DEADLOCK</a> error.  When using the Berkeley DB access
methods, this error return is propagated back through the Berkeley DB database
handle method to the calling application.</p>
<p>The deadlock detector identifies deadlocks by looking for a cycle in
what is commonly referred to as its "waits-for" graph.  More precisely,
the deadlock detector reads through the lock table, and reviews each
lock object currently locked.  Each object has lockers that currently
hold locks on the object and possibly a list of lockers waiting for a
lock on the object.  Each object's list of waiting lockers defines a
partial ordering.  That is, for a particular object, every waiting
locker comes after every holding locker because that holding locker must
release its lock before the waiting locker can make forward progress.
Conceptually, after each object has been examined, the partial orderings
are topologically sorted.  If this topological sort reveals any cycles,
the lockers forming the cycle are involved in a deadlock.  One of the
lockers is selected for rejection.</p>
<p>It is possible that rejecting a single lock request involved in a
deadlock is not enough to allow other lockers to make forward progress.
Unfortunately, at the time a lock request is selected for rejection,
there is not enough information available to determine whether rejecting
that single lock request will allow forward progress or not.  Because
most applications have few deadlocks, Berkeley DB takes the conservative
approach, rejecting as few requests as may be necessary to resolve the
existing deadlocks.  In particular, for each unique cycle found in the
waits-for graph described in the previous paragraph, only one lock
request is selected for rejection.  However, if there are multiple
cycles, one lock request from each cycle is selected for rejection.
Only after the enclosing transactions have received the lock request
rejection return and aborted their transactions can it be determined
whether it is necessary to reject additional lock requests in order to
allow forward progress.</p>
<p>The <a href="../../utility/db_deadlock.html">db_deadlock</a> utility performs deadlock detection by calling
the underlying Berkeley DB <a href="../../api_c/lock_detect.html">DB_ENV-&gt;lock_detect</a> method at regular intervals
(<a href="../../api_c/lock_detect.html">DB_ENV-&gt;lock_detect</a> runs a single iteration of the Berkeley DB deadlock
detector).  Alternatively, applications can create their own deadlock
utility or thread by calling the <a href="../../api_c/lock_detect.html">DB_ENV-&gt;lock_detect</a> method directly, or by
using the <a href="../../api_c/env_set_lk_detect.html">DB_ENV-&gt;set_lk_detect</a> method to configure Berkeley DB to
automatically run the deadlock detector whenever there is a conflict
over a lock.  The tradeoffs between using the <a href="../../api_c/lock_detect.html">DB_ENV-&gt;lock_detect</a> and
<a href="../../api_c/env_set_lk_detect.html">DB_ENV-&gt;set_lk_detect</a> methods is that automatic deadlock detection will
resolve deadlocks more quickly (because the deadlock detector runs
as soon as the lock request blocks), however, automatic deadlock
detection often runs the deadlock detector when there is no need for
it, and for applications with large numbers of locks and/or where many
operations block temporarily on locks but are soon able to proceed,
automatic detection can decrease performance.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../lock/stdmode.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/timeout.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1>Copyright (c) 1996,2008 Oracle.  All rights reserved.</font>
</body>
</html>