[prev in list] [next in list] [prev in thread] [next in thread]
List: openldap-technical
Subject: timeout and network-timeout values of zero for syncrepl in LAN replication
From: Christopher Paul <chris.paul () rexconsulting ! net>
Date: 2024-04-08 5:08:41
Message-ID: 64da00eb-14b3-47d2-9439-f67850188e50 () rexconsulting ! net
[Download RAW message or body]
Hello OpenLDAP-technical list,
I'm curious about community perspectives on a specific LDAP replication
timeout and network-timeout settings:
Setting "timeout=0" or "network-timeout=0" within a syncrepl/olcSyncrepl
definition for replication settings is not the best practice for LAN
environments. These parameters, when set to zero, instruct syncrepl to
wait indefinitely for connections and replication operations to conclude.
Within a LAN context, establishing new connections should ideally occur
in less than a second. Delays beyond a couple of seconds should kick in
the retry logic. This suggests that a more fitting network-timeout range
is between 1 to 5 seconds.
Concerning the "timeout" parameter, the ideal range might be between 60
to 120 seconds, to handle operations exceeding a minute, but again,
kicking in retry logic if they exceed two minutes. I admit that my
stance on the "timeout" setting is tentative, given that search
operation duration hinges more on the provider's responsiveness rather
than network speed alone.
This approach ensures that LDAP replication remains both responsive and
resilient, without compromising on efficiency or performance. Thoughts?
--
Chris Paul | Rex Consulting |https://www.rexconsulting.net
[Attachment #3 (text/html)]
<!DOCTYPE html><html data-lt-installed="true"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="padding-bottom: 1px;">
<p><font size="2">Hello OpenLDAP-technical list,</font></p>
<p><font size="2">I'm curious about community perspectives on a
specific LDAP replication timeout and network-timeout settings:<br>
</font></p>
<p><font size="2">Setting "timeout=0" or "network-timeout=0" \
within a syncrepl/olcSyncrepl definition for replication settings is
not the best practice for LAN environments. These parameters,
when set to zero, instruct syncrepl to wait </font><font \
size="2">indefinitely </font><font size="2"> for connections and replication \
operations to conclude. </font></p> <p><font size="2">Within a LAN context, \
establishing new connections should ideally occur in less than a second. Delays \
beyond a couple of seconds should kick in the retry logic. This suggests
that a more fitting network-timeout range is between 1 to 5
seconds.</font></p>
<p><font size="2">Concerning the "timeout" parameter, the ideal
range might be between 60 to 120 seconds, to handle operations
exceeding a minute, but again, kicking in retry logic if they
exceed two minutes. I admit that my stance on the "timeout"
setting is tentative, given that search operation duration
hinges more on the provider's responsiveness rather than network
speed alone.</font></p>
<p><font size="2">This approach ensures that LDAP replication
remains both responsive and resilient, without compromising on
efficiency or performance. Thoughts?</font></p>
<pre class="moz-signature" cols="72">--
Chris Paul | Rex Consulting | <a class="moz-txt-link-freetext" \
href="https://www.rexconsulting.net">https://www.rexconsulting.net</a></pre> </body>
<lt-container></lt-container>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic