diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/log_limits.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/log_limits.html')
| -rw-r--r-- | docs/programmer_reference/log_limits.html | 78 |
1 files changed, 48 insertions, 30 deletions
diff --git a/docs/programmer_reference/log_limits.html b/docs/programmer_reference/log_limits.html index 54f523d6..f29e3e44 100644 --- a/docs/programmer_reference/log_limits.html +++ b/docs/programmer_reference/log_limits.html @@ -14,7 +14,7 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="log_config.html">Prev</a> </td> - <th width="60%" align="center">Chapter 17. - The Logging Subsystem - </th> + <th width="60%" align="center">Chapter 17. The Logging Subsystem </th> <td width="20%" align="right"> <a accesskey="n" href="mp.html">Next</a></td> </tr> </table> @@ -38,32 +36,54 @@ </div> </div> </div> - <p>Log filenames 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> - <p>The log filename consists of <span class="bold"><strong>log.</strong></span> 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, in which each transaction is logging approximately 500 bytes of data. -The following calculation:</p> + <p> + Log filenames 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> + <p> + The log filename consists of <span class="bold"><strong>log.</strong></span> + 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, in which each transaction is logging + approximately 500 bytes of data. The following + calculation: + </p> <pre class="programlisting">(10 * 2^20 * 2000000000) / (6000 * 500 * 365 * 60 * 60 * 24) = ~221</pre> - <p>indicates that the system will run out of log filenames in roughly 221 -years.</p> - <p>There is no way to reset the log filename space in Berkeley DB. If your -application is reaching the end of its log filename space, you must do -the following:</p> + <p> + indicates that the system will run out of log filenames in + roughly 221 years. + </p> + <p> + There is no way to reset the log filename space in Berkeley + DB. If your application is reaching the end of its log + filename space, you must do the following: + </p> <div class="orderedlist"> <ol type="1"> - <li>Archive your databases as if to prepare for catastrophic failure (see -<a class="xref" href="transapp_archival.html" title="Database and log file archival">Database and log file archival</a> -for more information).</li> - <li>Reset the database's log sequence numbers (see the <span class="bold"><strong>-r</strong></span> option -to the <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility for more information).</li> - <li>Remove all of the log files from the database environment. (This is the -only situation in which all the log files are removed from an environment; -in all other cases, at least a single log file is retained.)</li> - <li>Restart your application.</li> + <li> + Archive your databases as if to prepare for + catastrophic failure (see <a class="xref" href="transapp_archival.html" title="Database and log file archival">Database and log file + archival</a> for more + information). + </li> + <li> + Reset the database's log sequence numbers (see the + <span class="bold"><strong>-r</strong></span> option to the + <a href="../api_reference/C/db_load.html" class="olink">db_load</a> utility for more information). + </li> + <li> + Remove all of the log files from the database + environment. (This is the only situation in which all the + log files are removed from an environment; in all other + cases, at least a single log file is retained.) + </li> + <li> + Restart your application. + </li> </ol> </div> </div> @@ -82,9 +102,7 @@ in all other cases, at least a single log file is retained.)</li> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Chapter 18. - The Memory Pool Subsystem - </td> + <td width="40%" align="right" valign="top"> Chapter 18. The Memory Pool Subsystem </td> </tr> </table> </div> |