summaryrefslogtreecommitdiff
path: root/db/docs/ref/rep/bulk.html
blob: 9fe243d0fdceb6d28585940b217a28d8b6bbce2d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
<!--$Id: bulk.so,v 1.4 2006/07/14 23:04:42 alanb Exp $-->
<!--Copyright 1997-2006 by Oracle Corporation-->
<!--All rights reserved.-->
<!--See the file LICENSE for redistribution information.-->
<html>
<head>
<title>Berkeley DB Reference Guide: Bulk transfer</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Berkeley DB Replication</dl></h3></td>
<td align=right><a href="../rep/init.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../rep/trans.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p>
<h3 align=center>Bulk transfer</h3>
<p>Sites in a replication group may be configured to use bulk transfer by
calling the <a href="../../api_c/rep_config.html">DB_ENV-&gt;rep_set_config</a> method with the <a href="../../api_c/rep_config.html#DB_REP_CONF_BULK">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_c/rep_limit.html">DB_ENV-&gt;rep_set_limit</a> method.</p>
<table width="100%"><tr><td><br></td><td align=right><a href="../rep/init.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../rep/trans.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
<p><font size=1>Copyright (c) 1996-2006 Oracle Corporation - All rights reserved.</font>
</body>
</html>