diff options
Diffstat (limited to 'docs/programmer_reference/rep_bulk.html')
| -rw-r--r-- | docs/programmer_reference/rep_bulk.html | 59 |
1 files changed, 34 insertions, 25 deletions
diff --git a/docs/programmer_reference/rep_bulk.html b/docs/programmer_reference/rep_bulk.html index 476666e6..630e91bf 100644 --- a/docs/programmer_reference/rep_bulk.html +++ b/docs/programmer_reference/rep_bulk.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="rep_init.html">Prev</a> </td> - <th width="60%" align="center">Chapter 12. - Berkeley DB Replication - </th> + <th width="60%" align="center">Chapter 12. Berkeley DB Replication </th> <td width="20%" align="right"> <a accesskey="n" href="rep_trans.html">Next</a></td> </tr> </table> @@ -38,27 +36,38 @@ </div> </div> </div> - <p>Sites in a replication group may be configured to use bulk transfer by -calling the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method with the <a href="../api_reference/C/repconfig.html#config_DB_REP_CONF_BULK" class="olink">DB_REP_CONF_BULK</a> -flag. When configured for bulk transfer, sites will accumulate records -in a buffer and transfer them to another site in a single network -transfer. Configuring bulk transfer makes sense for master sites, of -course. Additionally, applications using client-to-client -synchronization may find it helpful to configure bulk transfer for -client sites as well.</p> - <p>When a master is generating new log records, or any information request -is made of a master, and bulk transfer has been configured, records will -accumulate in a bulk buffer. The bulk buffer will be sent to the client -if either the buffer is full or if a permanent record (for example, a -transaction commit or checkpoint record) is queued for the client.</p> - <p>When a client is responding to another client's request for information, -and bulk transfer has been configured, records will accumulate in a bulk -buffer. The bulk buffer will be sent to the client when the buffer is -full or when the client's request has been satisfied; no particular type -of record will cause the buffer to be sent.</p> - <p>The size of the bulk buffer itself is internally determined and cannot -be configured. However, the overall size of a transfer may be limited -using the <a href="../api_reference/C/repset_limit.html" class="olink">DB_ENV->rep_set_limit()</a> method.</p> + <p> + Sites in a replication group may be configured to use bulk + transfer by calling the <a href="../api_reference/C/repconfig.html" class="olink">DB_ENV->rep_set_config()</a> method with the + <a href="../api_reference/C/repconfig.html#config_DB_REP_CONF_BULK" class="olink">DB_REP_CONF_BULK</a> flag. When configured for bulk transfer, + sites will accumulate records in a buffer and transfer them to + another site in a single network transfer. Configuring bulk + transfer makes sense for master sites, of course. + Additionally, applications using client-to-client + synchronization may find it helpful to configure bulk transfer + for client sites as well. + </p> + <p> + When a master is generating new log records, or any + information request is made of a master, and bulk transfer has + been configured, records will accumulate in a bulk buffer. The + bulk buffer will be sent to the client if either the buffer is + full or if a permanent record (for example, a transaction + commit or checkpoint record) is queued for the client. + </p> + <p> + When a client is responding to another client's request for + information, and bulk transfer has been configured, records + will accumulate in a bulk buffer. The bulk buffer will be sent + to the client when the buffer is full or when the client's + request has been satisfied; no particular type of record will + cause the buffer to be sent. + </p> + <p> + The size of the bulk buffer itself is internally determined + and cannot be configured. However, the overall size of a + transfer may be limited using the <a href="../api_reference/C/repset_limit.html" class="olink">DB_ENV->rep_set_limit()</a> method. + </p> </div> <div class="navfooter"> <hr /> |