003 File Manager
Current Path:
/usr/local/share/doc/db5/programmer_reference
usr
/
local
/
share
/
doc
/
db5
/
programmer_reference
/
📁
..
📄
BDB_Prog_Reference.pdf
(1.9 MB)
📄
am.html
(13.27 KB)
📄
am_close.html
(4.17 KB)
📄
am_conf.html
(13.76 KB)
📄
am_conf_logrec.html
(7.32 KB)
📄
am_conf_select.html
(24.85 KB)
📄
am_cursor.html
(36.58 KB)
📄
am_delete.html
(2.95 KB)
📄
am_foreign.html
(9.84 KB)
📄
am_get.html
(4.07 KB)
📄
am_misc.html
(6.3 KB)
📄
am_misc_bulk.html
(17.31 KB)
📄
am_misc_db_sql.html
(4.79 KB)
📄
am_misc_dbsizes.html
(4.06 KB)
📄
am_misc_diskspace.html
(11.57 KB)
📄
am_misc_error.html
(4.83 KB)
📄
am_misc_faq.html
(10.34 KB)
📄
am_misc_partial.html
(7.81 KB)
📄
am_misc_perm.html
(4.19 KB)
📄
am_misc_stability.html
(4.82 KB)
📄
am_misc_struct.html
(5.06 KB)
📄
am_misc_tune.html
(9.91 KB)
📄
am_opensub.html
(7.84 KB)
📄
am_partition.html
(17.19 KB)
📄
am_put.html
(4.68 KB)
📄
am_second.html
(14.76 KB)
📄
am_stat.html
(3.11 KB)
📄
am_sync.html
(3.63 KB)
📄
am_truncate.html
(2.54 KB)
📄
am_upgrade.html
(4.72 KB)
📄
am_verify.html
(4.77 KB)
📄
apprec.html
(8.14 KB)
📄
apprec_auto.html
(12.16 KB)
📄
apprec_config.html
(10 KB)
📄
apprec_def.html
(9.13 KB)
📄
arch.html
(11.09 KB)
📄
arch_apis.html
(10.27 KB)
📄
arch_bigpic.gif
(2.53 KB)
📄
arch_progmodel.html
(3.1 KB)
📄
arch_script.html
(4.39 KB)
📄
arch_smallpic.gif
(1.58 KB)
📄
arch_utilities.html
(8 KB)
📄
bdb_usenix.pdf
(79.81 KB)
📄
bt_conf.html
(29.94 KB)
📄
cam.html
(11.77 KB)
📄
cam_app.html
(16.91 KB)
📄
cam_fail.html
(7.77 KB)
📄
ch13s02.html
(4.19 KB)
📄
csharp.html
(7.48 KB)
📄
dumpload.html
(5.42 KB)
📄
dumpload_format.html
(6.58 KB)
📄
dumpload_text.html
(3.39 KB)
📄
embedded.html
(31.62 KB)
📄
env.html
(7.43 KB)
📄
env_create.html
(10.06 KB)
📄
env_db_config.html
(4.21 KB)
📄
env_encrypt.html
(10.19 KB)
📄
env_error.html
(4.77 KB)
📄
env_faq.html
(5.54 KB)
📄
env_naming.html
(15.54 KB)
📄
env_open.html
(4.95 KB)
📄
env_region.html
(8.11 KB)
📄
env_remote.html
(5.28 KB)
📄
env_security.html
(5.64 KB)
📄
env_size.html
(8.11 KB)
📄
ext.html
(7.13 KB)
📄
ext_perl.html
(3.84 KB)
📄
ext_php.html
(5.47 KB)
📄
general_am_conf.html
(21.43 KB)
📄
gettingStarted.css
(1.13 KB)
📄
group_membership.html
(20.37 KB)
📄
hash_conf.html
(6.96 KB)
📄
hash_usenix.pdf
(256.14 KB)
📄
heap_conf.html
(4.14 KB)
📄
index.html
(77.48 KB)
📄
intro.html
(9.57 KB)
📄
intro_dbis.html
(15.02 KB)
📄
intro_dbisnot.html
(13.49 KB)
📄
intro_distrib.html
(2.92 KB)
📄
intro_need.html
(5.06 KB)
📄
intro_products.html
(14.3 KB)
📄
intro_terrain.html
(19.43 KB)
📄
intro_what.html
(4.94 KB)
📄
intro_where.html
(3.75 KB)
📄
java.html
(7.62 KB)
📄
java_compat.html
(2.57 KB)
📄
java_faq.html
(7.5 KB)
📄
java_program.html
(6.69 KB)
📄
libtp_usenix.pdf
(243.14 KB)
📄
lock.html
(11.29 KB)
📄
lock_am_conv.html
(10.62 KB)
📄
lock_cam_conv.html
(4.95 KB)
📄
lock_config.html
(4.67 KB)
📄
lock_dead.html
(7.25 KB)
📄
lock_deaddbg.html
(10.32 KB)
📄
lock_max.html
(11.04 KB)
📄
lock_nondb.html
(4.94 KB)
📄
lock_notxn.html
(4.55 KB)
📄
lock_page.html
(5.71 KB)
📄
lock_stdmode.html
(5.27 KB)
📄
lock_timeout.html
(6.16 KB)
📄
lock_twopl.html
(4.48 KB)
📄
log.html
(7.08 KB)
📄
log_config.html
(5.06 KB)
📄
log_limits.html
(4.24 KB)
📄
magic.s5.be.txt
(3.54 KB)
📄
magic.s5.le.txt
(3.56 KB)
📄
magic.txt
(1.98 KB)
📄
moreinfo.html
(7.45 KB)
📄
mp.html
(8.86 KB)
📄
mp_config.html
(6.08 KB)
📄
mp_warm.html
(13.45 KB)
📄
preface.html
(5.1 KB)
📄
program.html
(7.21 KB)
📄
program_cache.html
(3.3 KB)
📄
program_compatible.html
(3.66 KB)
📄
program_copy.html
(7.35 KB)
📄
program_environ.html
(3.58 KB)
📄
program_errorret.html
(10.38 KB)
📄
program_faq.html
(4.58 KB)
📄
program_mt.html
(7.54 KB)
📄
program_namespace.html
(5.66 KB)
📄
program_perfmon.html
(32.07 KB)
📄
program_ram.html
(12.58 KB)
📄
program_runtime.html
(7.09 KB)
📄
program_scope.html
(9.8 KB)
📄
refs.html
(11.84 KB)
📄
rep.html
(16.57 KB)
📄
rep_app.html
(9.75 KB)
📄
rep_base_meth.html
(8.59 KB)
📄
rep_bulk.html
(4.01 KB)
📄
rep_clock_skew.html
(5.38 KB)
📄
rep_comm.html
(11.28 KB)
📄
rep_elect.html
(13.17 KB)
📄
rep_ex.html
(9.64 KB)
📄
rep_ex_chan.html
(8.52 KB)
📄
rep_ex_comm.html
(7.58 KB)
📄
rep_ex_rq.html
(5.52 KB)
📄
rep_faq.html
(9.2 KB)
📄
rep_filename.html
(7.7 KB)
📄
rep_id.html
(4.76 KB)
📄
rep_init.html
(5.14 KB)
📄
rep_lease.html
(18.32 KB)
📄
rep_mastersync.html
(11.24 KB)
📄
rep_mgr_ack.html
(8.5 KB)
📄
rep_mgr_meth.html
(11.06 KB)
📄
rep_mgrmulti.html
(10.28 KB)
📄
rep_newsite.html
(5.29 KB)
📄
rep_partition.html
(9.21 KB)
📄
rep_pri.html
(3.64 KB)
📄
rep_replicate.html
(18.8 KB)
📄
rep_ryw.html
(9.82 KB)
📄
rep_trans.html
(21.58 KB)
📄
rep_twosite.html
(6.76 KB)
📄
repmgr_channels.html
(13.34 KB)
📄
rq_conf.html
(18.29 KB)
📄
second.javas
(3.87 KB)
📄
sequence.html
(4.43 KB)
📄
solaris.txt
(5.62 KB)
📄
stl.html
(16.28 KB)
📄
stl_complex_rw.html
(19.31 KB)
📄
stl_container_specific.html
(9.04 KB)
📄
stl_db_advanced_usage.html
(9.68 KB)
📄
stl_db_usage.html
(13.27 KB)
📄
stl_efficienct_use.html
(11.87 KB)
📄
stl_examples.html
(8.24 KB)
📄
stl_known_issues.html
(4.54 KB)
📄
stl_memory_mgmt.html
(9.22 KB)
📄
stl_misc.html
(8.22 KB)
📄
stl_mt_usage.html
(9.06 KB)
📄
stl_persistence.html
(14.74 KB)
📄
stl_primitive_rw.html
(8.18 KB)
📄
stl_txn_usage.html
(4.88 KB)
📄
stl_usecase.html
(3.67 KB)
📄
tcl.html
(7.88 KB)
📄
tcl_error.html
(5.2 KB)
📄
tcl_faq.html
(4.89 KB)
📄
tcl_program.html
(3.78 KB)
📄
tcl_using.html
(4.43 KB)
📄
transapp.cs
(10.34 KB)
📄
transapp.html
(8.55 KB)
📄
transapp_admin.html
(4.8 KB)
📄
transapp_app.html
(25.08 KB)
📄
transapp_archival.html
(15.5 KB)
📄
transapp_atomicity.html
(5.46 KB)
📄
transapp_checkpoint.html
(6.18 KB)
📄
transapp_cursor.html
(6.79 KB)
📄
transapp_data_open.html
(7.52 KB)
📄
transapp_deadlock.html
(7.35 KB)
📄
transapp_env_open.html
(8.39 KB)
📄
transapp_fail.html
(6.8 KB)
📄
transapp_faq.html
(11.26 KB)
📄
transapp_filesys.html
(5.89 KB)
📄
transapp_hotfail.html
(10.54 KB)
📄
transapp_inc.html
(8.09 KB)
📄
transapp_journal.html
(4.72 KB)
📄
transapp_logfile.html
(5.3 KB)
📄
transapp_nested.html
(5.42 KB)
📄
transapp_put.html
(12.47 KB)
📄
transapp_read.html
(9.9 KB)
📄
transapp_reclimit.html
(12.6 KB)
📄
transapp_recovery.html
(8.74 KB)
📄
transapp_term.html
(6.02 KB)
📄
transapp_throughput.html
(9.06 KB)
📄
transapp_tune.html
(13.99 KB)
📄
transapp_why.html
(3.94 KB)
📄
txn.html
(8.63 KB)
📄
txn_config.html
(4.5 KB)
📄
txn_limits.html
(5.77 KB)
📄
witold.html
(745 B)
📄
writetest.cs
(2.26 KB)
📄
xa.html
(6.69 KB)
📄
xa_build.html
(19.12 KB)
📄
xa_faq.html
(7.27 KB)
📄
xa_xa_config.html
(8.1 KB)
📄
xa_xa_intro.html
(4.46 KB)
📄
xa_xa_restrict.html
(6.02 KB)
Editing: rep.html
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Chapter 12. Berkeley DB Replication</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> <link rel="up" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> <link rel="prev" href="transapp_faq.html" title="Transaction FAQ" /> <link rel="next" href="rep_id.html" title="Replication environment IDs" /> </head> <body> <div xmlns="" class="navheader"> <div class="libver"> <p>Library Version 11.2.5.3</p> </div> <table width="100%" summary="Navigation header"> <tr> <th colspan="3" align="center">Chapter 12. Berkeley DB Replication </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="transapp_faq.html">Prev</a> </td> <th width="60%" align="center"> </th> <td width="20%" align="right"> <a accesskey="n" href="rep_id.html">Next</a></td> </tr> </table> <hr /> </div> <div class="chapter" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h2 class="title"><a id="rep"></a>Chapter 12. Berkeley DB Replication </h2> </div> </div> </div> <div class="toc"> <p> <b>Table of Contents</b> </p> <dl> <dt> <span class="sect1"> <a href="rep.html#rep_intro">Replication introduction</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_id.html">Replication environment IDs</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_pri.html">Replication environment priorities</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_app.html">Building replicated applications</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_mgr_meth.html">Replication Manager methods</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_base_meth.html">Base API Methods</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_comm.html">Building the communications infrastructure</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_newsite.html">Connecting to a new site</a> </span> </dt> <dt> <span class="sect1"> <a href="group_membership.html">Managing Replication Manager Group Membership</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="group_membership.html#group_mem_add">Adding Sites to a Replication Group</a> </span> </dt> <dt> <span class="sect2"> <a href="group_membership.html#group_mem_remove">Removing Sites from a Replication Group</a> </span> </dt> <dt> <span class="sect2"> <a href="group_membership.html#group_mem_primordialstartup">Primordial Startups</a> </span> </dt> <dt> <span class="sect2"> <a href="group_membership.html#group_mem_upgrade">Upgrading Groups</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_filename.html">Managing Replication Files</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_mgrmulti.html">Running Replication Manager in multiple processes</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="rep_mgrmulti.html#idp52420616">One replication process and multiple subordinate processes</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mgrmulti.html#idp52417008">Persistence of local site network address configuration</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mgrmulti.html#idp52400144">Programming considerations</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mgrmulti.html#idp52414488">Handling failure</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mgrmulti.html#idp52412256">Other miscellaneous rules</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_replicate.html">Running Replication using the db_replicate Utility</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="rep_replicate.html#idp52430544">One Replication Process and Multiple Subordinate Processes</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_replicate.html#idp52447760">Common Use Case</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_replicate.html#idp52457840">Avoiding Rollback</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_replicate.html#idp52462952">When to Consider an Integrated HA Application</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_mgr_ack.html">Choosing a Replication Manager Ack Policy</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_elect.html">Elections</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_mastersync.html">Synchronizing with a master</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="rep_mastersync.html#rep_delay_sync">Delaying client synchronization</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mastersync.html#rep_c2c_sync">Client-to-client synchronization</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mastersync.html#idp52488504">Blocked client operations</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_mastersync.html#idp52510624">Clients too far out-of-date to synchronize</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_init.html">Initializing a new site</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_bulk.html">Bulk transfer</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_trans.html">Transactional guarantees</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_lease.html">Master Leases</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="rep_lease.html#masterlease_change_groupsize">Changing Group Size</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_ryw.html">Read your writes consistency</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="rep_ryw.html#gettoken">Getting a token</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_ryw.html#tokenhandling">Token handling</a> </span> </dt> <dt> <span class="sect2"> <a href="rep_ryw.html#usingtoken">Using a token to check or wait for a transaction</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_clock_skew.html">Clock Skew</a> </span> </dt> <dt> <span class="sect1"> <a href="repmgr_channels.html">Using Replication Manager message channels</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="repmgr_channels.html#dbchannel_class">DB_CHANNEL</a> </span> </dt> <dt> <span class="sect2"> <a href="repmgr_channels.html#dbchannel_send">Sending messages over a message channel</a> </span> </dt> <dt> <span class="sect2"> <a href="repmgr_channels.html#dbchannel_receive">Receiving messages</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="rep_twosite.html">Special considerations for two-site replication groups</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_partition.html">Network partitions</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_faq.html">Replication FAQ</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_ex.html">Ex_rep: a replication example</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_ex_comm.html">Ex_rep_base: a TCP/IP based communication infrastructure</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_ex_rq.html">Ex_rep_base: putting it all together</a> </span> </dt> <dt> <span class="sect1"> <a href="rep_ex_chan.html">Ex_rep_chan: a Replication Manager channel example</a> </span> </dt> </dl> </div> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h2 class="title" style="clear: both"><a id="rep_intro"></a>Replication introduction</h2> </div> </div> </div> <p>Berkeley DB includes support for building highly available applications based on replication. Berkeley DB replication groups consist of some number of independently configured database environments. There is a single <span class="emphasis"><em>master</em></span> database environment and one or more <span class="emphasis"><em>client</em></span> database environments. Master environments support both database reads and writes; client environments support only database reads. If the master environment fails, applications may upgrade a client to be the new master. The database environments might be on separate computers, on separate hardware partitions in a non-uniform memory access (NUMA) system, or on separate disks in a single server. As always with Berkeley DB environments, any number of concurrent processes or threads may access a database environment. In the case of a master environment, any number of threads of control may read and write the environment, and in the case of a client environment, any number of threads of control may read the environment.</p> <p>Applications may be written to provide various degrees of consistency between the master and clients. The system can be run synchronously such that replicas are guaranteed to be up-to-date with all committed transactions, but doing so may incur a significant performance penalty. Higher performance solutions sacrifice total consistency, allowing the clients to be out of date for an application-controlled amount of time.</p> <p> There are two ways to build replicated applications. The simpler way is to use the Berkeley DB Replication Manager. The Replication Manager provides a standard communications infrastructure, and it creates and manages the background threads needed for processing replication messages. </p> <p>The Replication Manager implementation is based on TCP/IP sockets, and uses POSIX 1003.1 style networking and thread support. (On Windows systems, it uses standard Windows thread support.) As a result, it is not as portable as the rest of the Berkeley DB library itself.</p> <p>The alternative is to use the lower-level replication "Base APIs". This approach affords more flexibility, but requires the application to provide some critical components:</p> <div class="orderedlist"> <ol type="1"> <li>A communication infrastructure. Applications may use whatever wire protocol is appropriate for their application (for example, RPC, TCP/IP, UDP, VI or message-passing over the backplane).</li> <li>The application is responsible for naming. Berkeley DB refers to the members of a replication group using an application-provided ID, and applications must map that ID to a particular database environment or communication channel.</li> <li>The application is responsible for monitoring the status of the master and clients, and identifying any unavailable database environments.</li> <li>The application must provide whatever security policies are needed. For example, the application may choose to encrypt data, use a secure socket layer, or do nothing at all. The level of security is left to the sole discretion of the application.</li> </ol> </div> <p>(Note that Replication Manager does not provide wire security for replication messages.)</p> <p>The following pages present various programming considerations, many of which are directly relevant only for Base API applications. However, even when using Replication Manager it is important to understand the concepts.</p> <p>Finally, the Berkeley DB replication implementation has one other additional feature to increase application reliability. Replication in Berkeley DB is implemented to perform database updates using a different code path than the standard ones. This means operations that manage to crash the replication master due to a software bug will not necessarily also crash replication clients.</p> <p>For more information on the replication manager operations, see the <a href="../api_reference/C/rep.html#replist" class="olink">Replication and Related Methods</a> section in the <em class="citetitle">Berkeley DB C API Reference Guide.</em> </p> </div> </div> <div class="navfooter"> <hr /> <table width="100%" summary="Navigation footer"> <tr> <td width="40%" align="left"><a accesskey="p" href="transapp_faq.html">Prev</a> </td> <td width="20%" align="center"> </td> <td width="40%" align="right"> <a accesskey="n" href="rep_id.html">Next</a></td> </tr> <tr> <td width="40%" align="left" valign="top">Transaction FAQ </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> <td width="40%" align="right" valign="top"> Replication environment IDs</td> </tr> </table> </div> </body> </html>
Upload File
Create Folder
