In order to allow concurrent operations, DB provides the locking subsystem. This subsystem provides inter- and intra- process concurrency mechanisms. It is extensively used by DB concurrent applications, but it can also be generally used for non-DB resources.
This section describes the locking subsystem as it is used to protect DB resources. In particular, issues on configuration are examined here. For information on using the locking subsystem to manage non-DB resources, see the Berkeley DB Programmer's Reference Guide.
You initialize the locking subsystem by specifying
true to the
EnvironmentConfig.setInitializeLocking()
method.
Before opening your environment, you can configure various maximum values for your locking subsystem. Note that these limits can only be configured before the environment is opened. Also, these methods configure the entire environment, not just a specific environment handle.
Finally, each bullet below identifies the
DB_CONFIG file parameter that can be used
to specify the specific locking limit. If used, these
DB_CONFIG file parameters override any
value that you might specify using the environment handle.
The limits that you can configure are as follows:
The maximum number of lockers supported by the environment. This value is used by the environment when it is opened to estimate the amount of space that it should allocate for various internal data structures. By default, 1,000 lockers are supported.
To configure this value, use the
EnvironmentConfig.setMaxLockers()
method.
As an alternative to this method, you can configure this
value using the DB_CONFIG file's
set_lk_max_lockers parameter.
The maximum number of locks supported by the environment. By default, 1,000 locks are supported.
To configure this value, use the
EnvironmentConfig.setMaxLocks()
method.
As an alternative to this method, you can configure this
value using the DB_CONFIG file's
set_lk_max_locks parameter.
The maximum number of locked objects supported by the environment. By default, 1,000 objects can be locked.
To configure this value, use the
EnvironmentConfig.setMaxLockObjects()
method.
As an alternative to this method, you can configure this
value using the DB_CONFIG file's
set_lk_max_objects parameter.
For a definition of lockers, locks, and locked objects, see Lock Resources.
For example, to configure the maximum number of locks that your environment can use:
package db.txn;
import com.sleepycat.db.DatabaseException;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import java.io.File;
import java.io.FileNotFoundException;
...
Environment myEnv = null;
try {
EnvironmentConfig myEnvConfig = new EnvironmentConfig();
myEnvConfig.setTransactional(true);
myEnvConfig.setMaxLocks(5000);
myEnv = new Environment(new File("/my/env/home"),
myEnvConfig);
} catch (DatabaseException de) {
// Exception handling goes here
} catch (FileNotFoundException fnfe) {
// Exception handling goes here
}
In order for DB to know that a deadlock has occurred, some mechanism must be used to perform deadlock detection. There are three ways that deadlock detection can occur:
Allow DB to internally detect deadlocks as they occur.
To do this, you use
EnvironmentConfig.setLockDetectMode().
This method causes DB to walk its internal lock table
looking for a deadlock whenever a lock request
is blocked. This method also identifies how DB decides which lock
requests are rejected when deadlocks are detected. For example,
DB can decide to reject the lock request for the transaction
that has the most number of locks, the least number of locks,
holds the oldest lock, holds the most number of write locks, and
so forth (see the API reference documentation for a complete
list of the lock detection policies).
You can call this method at any time during your application's lifetime, but typically it is used before you open your environment.
Note that how you want DB to decide which thread of control should break a deadlock is extremely dependent on the nature of your application. It is not unusual for some performance testing to be required in order to make this determination. That said, a transaction that is holding the maximum number of locks is usually indicative of the transaction that has performed the most amount of work. Frequently you will not want a transaction that has performed a lot of work to abandon its efforts and start all over again. It is not therefore uncommon for application developers to initially select the transaction with the minimum number of write locks to break the deadlock.
Using this mechanism for deadlock detection means that your application will never have to wait on a lock before discovering that a deadlock has occurred. However, walking the lock table every time a lock request is blocked can be expensive from a performance perspective.
Use a dedicated thread or external process to perform deadlock detection. Note that this thread must be performing no other database operations beyond deadlock detection.
To externally perform lock detection, you can use
either the
Environment.detectDeadlocks()
method, or use the
db_deadlock command line
utility. This method (or command) causes DB to walk the
lock table looking for deadlocks.
Note that like
EnvironmentConfig.setLockDetectMode(),
you also use this method (or command line utility)
to identify which lock requests are rejected in the
event that a deadlock is detected.
Applications that perform deadlock detection in this way typically run deadlock detection between every few seconds and a minute. This means that your application may have to wait to be notified of a deadlock, but you also save the overhead of walking the lock table every time a lock request is blocked.
Lock timeouts.
You can configure your locking subsystem such that
it times out any lock that is not released within a
specified amount of time. To do this, use the
EnvironmentConfig.setLockTimeout()
method.
Note that lock timeouts are only checked when a
lock request is blocked or when deadlock
detection is otherwise performed. Therefore, a lock can have timed out and still be held for
some length of time until DB has a reason to examine its locking tables.
Be aware that extremely long-lived transactions, or operations that hold locks for a long time, may be inappropriately timed out before the transaction or operation has a chance to complete. You should therefore use this mechanism only if you know your application will hold locks for very short periods of time.
For example, to configure your application such that DB checks the lock table for deadlocks every time a lock request is blocked:
package db.txn;
import com.sleepycat.db.Environment;
import com.sleepycat.db.EnvironmentConfig;
import com.sleepycat.db.LockDetectMode;
import java.io.File;
...
Environment myEnv = null;
try {
EnvironmentConfig myEnvConfig = new EnvironmentConfig();
myEnvConfig.setTransactional(true);
myEnvConfig.setInitializeCache(true);
myEnvConfig.setInitializeLocking(true);
myEnvConfig.setInitializeLogging(true);
// Configure db to perform deadlock detection internally, and to
// choose the transaction that has performed the least amount
// of writing to break the deadlock in the event that one
// is detected.
envConfig.setLockDetectMode(LockDetectMode.MINWRITE);
myEnv = new Environment(new File("/my/env/home"),
myEnvConfig);
// From here, you open your databases, proceed with your
// database operations, and respond to deadlocks as
// is normal (omitted for brevity).
...
Finally, the following command line call causes
deadlock detection to be run against the
environment contained in /export/dbenv. The
transaction with the youngest lock is chosen to break the
deadlock:
> /usr/local/db_install/bin/db_deadlock -h /export/dbenv -a y
For more information, see the
db_deadlock reference documentation.
When DB determines that a deadlock has occurred, it will
select a thread of control to resolve the deadlock and then
throws DeadlockException in that
thread.
If a deadlock is detected, the thread must:
Cease all read and write operations.
Close all open cursors.
Abort the transaction.
Optionally retry the operation. If your application retries deadlocked operations, the new attempt must be made using a new transaction.
If a thread has deadlocked, it may not make any additional database calls using the handle that has deadlocked.
For example:
// retry_count is a counter used to identify how many times
// we've retried this operation. To avoid the potential for
// endless looping, we won't retry more than MAX_DEADLOCK_RETRIES
// times.
// txn is a transaction handle.
// key and data are DatabaseEntry handles. Their usage is not shown here.
while (retry_count < MAX_DEADLOCK_RETRIES) {
try {
txn = myEnv.beginTransaction(null, null);
myDatabase.put(txn, key, data);
txn.commit();
return 0;
} catch (DeadlockException de) {
try {
// Abort the transaction and increment the
// retry counter
txn.abort();
retry_count++;
if (retry_count >= MAX_DEADLOCK_RETRIES) {
System.err.println("Exceeded retry limit. Giving up.");
return -1;
}
} catch (DatabaseException ae) {
System.err.println("txn abort failed: " + ae.toString());
return -1;
}
} catch (DatabaseException e) {
try {
// Abort the transaction.
txn.abort();
} catch (DatabaseException ae) {
System.err.println("txn abort failed: " + ae.toString());
return -1;
}
}
}