<?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>rep_set_request</title>
<link rel="stylesheet" href="apiReference.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Berkeley DB C API Reference" />
<link rel="up" href="configuration_reference.html" title="Appendix D. DB_CONFIG Parameter Reference" />
<link rel="prev" href="rep_set_priority_parameter.html" title="rep_set_priority" />
<link rel="next" href="rep_set_timeout_parameter.html" title="rep_set_timeout" />
</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">rep_set_request</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="rep_set_priority_parameter.html">Prev</a> </td>
<th width="60%" align="center">Appendix D. DB_CONFIG Parameter Reference</th>
<td width="20%" align="right"> <a accesskey="n" href="rep_set_timeout_parameter.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="rep_set_request_parameter"></a>rep_set_request</h2>
</div>
</div>
</div>
<p>
Sets a threshold for the minimum and maximum
time that a client waits before requesting retransmission of a missing message.
</p>
<p>
The syntax of this parameter in the <a href="../../programmer_reference/env_db_config.html#env_db_config.DB_CONFIG" class="olink">DB_CONFIG</a> file is a
single line with the string
<code class="literal">rep_set_request</code>, one or more whitespace
characters, and the request time specified in two parts:
the min and the max. 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.
</p>
<p>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.
</p>
<p>For more information, see <a class="xref" href="repset_request.html" title="DB_ENV->rep_set_request()">DB_ENV->rep_set_request()</a>. </p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="rep_set_priority_parameter.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="configuration_reference.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="rep_set_timeout_parameter.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">rep_set_priority </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> rep_set_timeout</td>
</tr>
</table>
</div>
</body>
</html>
distrib
>
Mageia
>
6
>
x86_64
>
media
>
core-updates
>
by-pkgid
>
34843f660b92a2d45c266a31c0f1e1ef
>
files
>
398
