From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/rep_bulk.html | 59 +++++++++++++++++++-------------- 1 file changed, 34 insertions(+), 25 deletions(-) (limited to 'docs/programmer_reference/rep_bulk.html') 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 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +
Prev Chapter 12.  - Berkeley DB Replication - Chapter 12.  Berkeley DB Replication  Next
@@ -38,27 +36,38 @@
-

Sites in a replication group may be configured to use bulk transfer by -calling the DB_ENV->rep_set_config() method with the DB_REP_CONF_BULK -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.

-

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.

-

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.

-

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 DB_ENV->rep_set_limit() method.

+

+ Sites in a replication group may be configured to use bulk + transfer by calling the DB_ENV->rep_set_config() method with the + DB_REP_CONF_BULK 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. +

+

+ 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. +

+

+ 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. +

+

+ 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 DB_ENV->rep_set_limit() method. +

-- cgit v1.2.1