Edit File - File Manager

Edit File: rep_request.html

<html>
<head>
<title>Berkeley DB: DB_ENV-&gt;rep_set_request</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>
DB_ENV-&gt;rep_set_request
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db.h&gt;

int
DB_ENV-&gt;rep_set_request(DB_ENV *env, u_int32_t min, u_int32_t max);

int
DB_ENV-&gt;rep_get_request(DB_ENV *env, u_int32_t *minp, u_int32_t *maxp);
</pre>
<hr size=1 noshade>
Description: DB_ENV-&gt;rep_set_request
The DB_ENV-&gt;rep_set_request method sets a threshold for the minimum and maximum
time that a client waits before requesting retransmission of a missing
message. Specifically, if the client detects a gap in the sequence
of incoming log records or database pages, Berkeley DB will
wait for at least min microseconds before requesting
retransmission of the missing record. Berkeley DB will double that
amount before requesting the same missing record again, and so on, up
to a maximum threshold of max microseconds.
These values are thresholds only. Since Berkeley DB has no thread available in
the library as a timer, the threshold is only checked when a thread
enters the Berkeley DB library to process an incoming replication message.
Any amount of time may have passed since the last message arrived and
Berkeley DB only checks whether the amount of time since a request was made
is beyond the threshold value or not.
By default the minimum is 40000 and the maximum is 1280000 (1.28 seconds).
These defaults are fairly arbitrary and the application likely needs
to adjust these. The values should be based on expected load and
performance characteristics of the master and client host platforms
and transport infrastructure as well as round-trip message time.
The database environment's replication subsystem may also be configured using the
environment's <a href="../../db4-devel-4.7.25/ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file. The syntax of the entry in that
file is a single line with the string "rep_set_request", one or more whitespace
characters, and the request times specified in two parts: the min and the max.
For example, "rep_set_request 40000 1280000".
Because the <a href="../../db4-devel-4.7.25/ref/env/db_config.html#DB_CONFIG">DB_CONFIG</a> file is read when the database environment
is opened, it will silently overrule configuration done before that
time.
The DB_ENV-&gt;rep_set_request method configures a database environment, not only operations
performed using the specified <a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a> handle.
The DB_ENV-&gt;rep_set_request method may be called at any time during the life of the
application.
The DB_ENV-&gt;rep_set_request method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 max<ul compact><li>The maximum number of microseconds a client waits before
requesting retransmission.</ul>
 min<ul compact><li>The minimum number of microseconds a client waits before
requesting retransmission.</ul>
 
 Errors
The DB_ENV-&gt;rep_set_request method
may fail and return one of the following non-zero errors:
 
EINVAL<ul compact><li>An
invalid flag value or parameter was specified.</ul>
 
<hr size=1 noshade>
Description: DB_ENV-&gt;rep_get_request
The DB_ENV-&gt;rep_get_request method returns the minimum and maximum number of
microseconds a client waits before requesting retransmission.
The DB_ENV-&gt;rep_get_request method may be called at any time during the life of the
application.
The DB_ENV-&gt;rep_get_request method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 maxp<ul compact><li>The maxp parameter references memory into which
 the maximum number of microseconds a client will wait before requesting
retransmission is copied.</ul> 
 minp<ul compact><li>The minp parameter references memory into which
 the minimum number of microseconds a client will wait before requesting
retransmission is copied.</ul> 
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/rep_list.html">Replication and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager