diff options
Diffstat (limited to 'bdb/docs/ref/log')
| -rw-r--r-- | bdb/docs/ref/log/config.html | 40 | ||||
| -rw-r--r-- | bdb/docs/ref/log/intro.html | 58 | ||||
| -rw-r--r-- | bdb/docs/ref/log/limits.html | 47 |
3 files changed, 0 insertions, 145 deletions
diff --git a/bdb/docs/ref/log/config.html b/bdb/docs/ref/log/config.html deleted file mode 100644 index f3c94889312..00000000000 --- a/bdb/docs/ref/log/config.html +++ /dev/null @@ -1,40 +0,0 @@ -<!--$Id: config.so,v 10.16 2001/01/18 20:31:37 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Configuring logging</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Logging Subsystem</dl></h3></td> -<td width="1%"><a href="../../ref/log/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/log/limits.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Configuring logging</h1> -<p>The two aspects of logging that may be configured are the size of log -files on disk and the size of the log buffer in memory. The -<a href="../../api_c/env_set_lg_max.html">DBENV->set_lg_max</a> interface specifies the individual log file -size for all of the applications sharing the Berkeley DB environment. Setting -the log file size is largely a matter of convenience, and a reflection -of the application's preferences in backup media and frequency. -However, setting the log file size too low can potentially cause -problems as it would be possible to run out of log sequence numbers, -which requires a full archival and application restart to reset. See -the <a href="../../ref/log/limits.html">Log file limits</a> section for more -information. -<p>The <a href="../../api_c/env_set_lg_bsize.html">DBENV->set_lg_bsize</a> interface specifies the size of the -in-memory log buffer, in bytes. Log information is stored in memory -until the buffer fills up or transaction commit forces the buffer to be -written to disk. Larger buffer sizes can significantly increase -throughput in the presence of long running transactions, highly -concurrent applications, or transactions producing large amounts of -data. By default, the buffer is 32KB. -<table><tr><td><br></td><td width="1%"><a href="../../ref/log/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/log/limits.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> diff --git a/bdb/docs/ref/log/intro.html b/bdb/docs/ref/log/intro.html deleted file mode 100644 index 0c41c17efa0..00000000000 --- a/bdb/docs/ref/log/intro.html +++ /dev/null @@ -1,58 +0,0 @@ -<!--$Id: intro.so,v 10.16 2001/01/18 20:31:37 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Berkeley DB and logging</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Logging Subsystem</dl></h3></td> -<td width="1%"><a href="../../ref/lock/nondb.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/log/config.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Berkeley DB and logging</h1> -<p>The logging subsystem is the logging facility used by Berkeley DB. It is -largely Berkeley DB specific, although it is potentially useful outside of -the Berkeley DB package for applications wanting write-ahead logging support. -Applications wanting to use the log for purposes other than logging file -modifications based on a set of open file descriptors will almost -certainly need to make source code modifications to the Berkeley DB code -base. -<p>A log can be shared by any number of threads of control. The -<a href="../../api_c/env_open.html">DBENV->open</a> interface is used to open a log. When the log is no -longer in use, it should be closed, using the <a href="../../api_c/env_close.html">DBENV->close</a> -interface. -<p>Individual log entries are identified by log sequence numbers. Log -sequence numbers are stored in an opaque object, a <a href="../../api_c/db_lsn.html">DB_LSN</a>. -<p>The <a href="../../api_c/log_put.html">log_put</a> interface is used to append new log records to the -log. Optionally, the <a href="../../api_c/log_put.html#DB_CHECKPOINT">DB_CHECKPOINT</a> flag can be used to output -a checkpoint log record (indicating that the log is consistent to that -point and recoverable after a system or application failure), as well -as open-file information. The <a href="../../api_c/log_get.html">log_get</a> interface is used to -retrieve log records from the log. -<p>There are additional interfaces for integrating the log subsystem with a -transaction processing system: -<p><dl compact> -<p><dt><a href="../../api_c/log_register.html">log_register</a> and <a href="../../api_c/log_unregister.html">log_unregister</a><dd>These interfaces associate files with identification numbers. These -identification numbers are logged so that transactional recovery -correctly associates log records with the appropriate files. -<p><dt><a href="../../api_c/log_flush.html">log_flush</a><dd>Flushes the log up to a particular log sequence number. -<p><dt><a href="../../api_c/log_compare.html">log_compare</a><dd>Allows applications to compare any two log sequence numbers. -<p><dt><a href="../../api_c/log_file.html">log_file</a> <dd>Maps a log sequence number to the specific log file which contains it. -<p><dt><a href="../../api_c/log_archive.html">log_archive</a><dd>Returns various sets of log file names. These interfaces are used for -database administration, e.g., to determine if log files may safely be -removed from the system. -<p><dt><a href="../../api_c/log_stat.html">log_stat</a> <dd>The display <a href="../../utility/db_stat.html">db_stat</a> utility uses the <a href="../../api_c/log_stat.html">log_stat</a> interface -to display statistics about the log. -<p><dt><a href="../../api_c/env_remove.html">DBENV->remove</a><dd>The log meta-information (but not the log files themselves) may be -removed using the <a href="../../api_c/env_remove.html">DBENV->remove</a> interface. -</dl> -<table><tr><td><br></td><td width="1%"><a href="../../ref/lock/nondb.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/log/config.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> diff --git a/bdb/docs/ref/log/limits.html b/bdb/docs/ref/log/limits.html deleted file mode 100644 index d34e5a81339..00000000000 --- a/bdb/docs/ref/log/limits.html +++ /dev/null @@ -1,47 +0,0 @@ -<!--$Id: limits.so,v 10.23 2001/01/18 20:31:37 bostic Exp $--> -<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.--> -<!--All rights reserved.--> -<html> -<head> -<title>Berkeley DB Reference Guide: Log file limits</title> -<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> -<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++"> -</head> -<body bgcolor=white> - <a name="2"><!--meow--></a> -<table><tr valign=top> -<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Logging Subsystem</dl></h3></td> -<td width="1%"><a href="../../ref/log/config.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/mp/intro.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p> -<h1 align=center>Log file limits</h1> -<p>Log file names and sizes impose a limit on how long databases may be -used in a Berkeley DB database environment. It is quite unlikely that an -application will reach this limit, however, if the limit is reached, -the Berkeley DB environment's databases must be dumped and reloaded. -<p>The log file name consists of <b>log.</b> followed by 10 digits, with -a maximum of 2,000,000,000 log files. Consider an application performing -6000 transactions per second, for 24 hours a day, logged into 10MB log -files, where each transaction is logging approximately 500 bytes of data. -The calculation: -<p><blockquote><pre>(10 * 2^20 * 2000000000) / (6000 * 500 * 365 * 60 * 60 * 24) = ~221</pre></blockquote> -<p>indicates that the system will run out of log file names in roughly 221 -years. -<p>There is no way to reset the log file name space in Berkeley DB. If your -application is reaching the end of its log file name space, you must: -<p><ol> -<p><li>Archive your databases as if to prepare for catastrophic failure (see -<a href="../../utility/db_archive.html">db_archive</a> for more information). -<p><li>Dump and re-load all your databases (see <a href="../../utility/db_dump.html">db_dump</a> and -<a href="../../utility/db_load.html">db_load</a> for more information). -<p><li>Remove all of the log files from the database environment. Note, this -is the only situation where all of the log files are removed from an -environment, in all other cases at least a single log file is -retained. -<p><li>Restart your application. -</ol> -<table><tr><td><br></td><td width="1%"><a href="../../ref/log/config.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/mp/intro.html"><img src="../../images/next.gif" alt="Next"></a> -</td></tr></table> -<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font> -</body> -</html> |