Bug 1258997 - New configuration parameter ReplicaWaitForAsyncResults in nsDS5ReplicationAgreement
Summary: New configuration parameter ReplicaWaitForAsyncResults in nsDS5ReplicationAgr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-config-command-file-reference
Version: 10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1171358
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-01 17:21 UTC by Noriko Hosoi
Modified: 2017-01-17 08:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 08:25:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Noriko Hosoi 2015-09-01 17:21:13 UTC
Description of problem:

In the replication topology, the waiting time for the consumer ready used to be hardcoded to 1 second, which could be too long in the advanced network environment.  To improve the throughput of the replication, a new config parameter nsDS5ReplicaWaitForAsyncResults (in milliseconds) is introduced to the nsDS5ReplicationAgreement.  The default value is 1 second.

Here's the detailed info.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Description: Introducing a config attr nsDS5ReplicaWaitForAsyncResults
to the agreement entry.
  dn: cn=<AGREEMENT>,cn=replica,cn="<SUFFIX>",cn=mapping tree,cn=config
  nsDS5ReplicaWaitForAsyncResults: <integer in millisecond>

Prior to this patch, supplier sleeps 1 second if it finds the response
from consumer is not ready.  1 second could be too long if higher
replication throughput is required.

This patch makes the waiting time configurable, and change the default
to 100 millisecond.  If the attribute nsDS5ReplicaWaitForAsyncResults
does not exist or the value is 0, the default value is set.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Comment 2 Marc Muehlfeld 2017-01-17 08:25:11 UTC
The update is now available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.