Bug 1349571 - Improve MMR replication convergence
Summary: Improve MMR replication convergence
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
Petr Bokoc
URL:
Whiteboard:
Depends On:
Blocks: 1351323 1356898
TreeView+ depends on / blocked
 
Reported: 2016-06-23 17:12 UTC by Noriko Hosoi
Modified: 2020-09-13 21:40 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-1.3.5.6-1.el7
Doc Type: Enhancement
Doc Text:
New attribute for configuring replica release timeout In a multi-master replication environment where multiple masters receive updates at the same time, it was previously possible for a single master to obtain exclusive access to a replica and hold it for a very long time due to problems such as a slow network connection. During this time, other masters were blocked from accessing the same replica, which considerably slowed down the replication process. This update adds a new configuration attribute, "nsds5ReplicaReleaseTimeout", which can be used to specify a timeout in seconds. After the specified timeout period passes, the master releases the replica, allowing other masters to access it and send their updates.
Clone Of:
: 1351323 1358392 (view as bug list)
Environment:
Last Closed: 2016-11-03 20:43:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1786 0 None None None 2020-09-13 21:40:09 UTC
Red Hat Product Errata RHSA-2016:2594 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-03 12:11:08 UTC

Description Noriko Hosoi 2016-06-23 17:12:47 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/48636

Replication latency, especially over a WAN, can become worse when there are several masters receiving updates at the same time.  What happens is that one master will take exclusive access of a replica, and not release it for a very long time.  This blocks the other masters from sending their updates to that consumer, and this adds to the replication latency as those updates have to travel back and forth with all the other masters, and consumers.  See the bugzilla for more detailed info.

We need a way to notify a master that it is holding its exclusive access of a replica for too long, and that it needs to yield so other masters can start sending some of their updates to that replica.
Comment 1 mreynolds 2016-06-23 18:26:06 UTC 
Fixed upstream:

Design doc for new feature:

http://www.port389.org/docs/389ds/design/repl-conv-design.html
Comment 2 Noriko Hosoi 2016-06-24 18:22:40 UTC 
Justification: Important customer reported the problem.
(See also https://bugzilla.redhat.com/show_bug.cgi?id=1157799)

This improvement is beneficial for all the customers who deploy the Directory Server/IPA with the replication.
Comment 17 errata-xmlrpc 2016-11-03 20:43:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2594.html
Note You need to log in before you can comment on or make changes to this bug.