RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 830348 - Slow shutdown when you have 100+ replication agreements
Summary: Slow shutdown when you have 100+ replication agreements
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-08 21:43 UTC by Nathan Kinder
Modified: 2020-09-13 20:05 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.2.11.12-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: a long sleep in the replication stop code Consequence: with many agmts, the server shutdown would take longer Fix: reduce a sleep interval. Result: faster shutdown
Clone Of:
Environment:
Last Closed: 2013-02-21 08:17:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 271 0 None None None 2020-09-13 20:05:26 UTC
Red Hat Product Errata RHSA-2013:0503 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2013-02-21 08:18:44 UTC

Description Nathan Kinder 2012-06-08 21:43:13 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/271

I have a 389 DS with 154 replication agreements and in the future I'll 400+. In the current configuration, DS takes 5 minutes to shutdown. If I disable the replication plugin (Multimaster) shutdown takes 3 seconds.

I need the agreements because in my scenario I have two servers in the headquarters of the company with the whole tree and, 150 servers replicating two specific subtrees each one.
Comment 2 RHEL Program Management 2012-07-10 07:10:35 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 RHEL Program Management 2012-07-10 23:00:54 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 4 Jenny Severance 2012-08-31 19:03:50 UTC 
Please add steps to verify  Is it possible to verify this bugzilla without 150 replicas?
Comment 5 Rich Megginson 2012-08-31 19:06:23 UTC 
Mark, did you check in a TET test for this issue?
Comment 7 mreynolds 2012-09-06 13:57:21 UTC 
I did not add a test suite, as I never tested 100 agmts.  We never got feedback from the customer after creating this fix.  So I do not know if this fix addressed the customer issue.  The fix was to reduce a sleep from 1 second to 100 ms in the repl stop protocol.
Comment 8 Sankar Ramalingam 2012-12-06 13:39:16 UTC 
time service dirsrv restart M1 # 100 Replication Agreements
Shutting down dirsrv: 
    M1...[  OK  ]
Starting dirsrv: 
    M1...[  OK  ]

real	0m15.893s
user	0m0.687s
sys	0m0.174s

time service dirsrv restart M1 # 500 Replication Agreements
Shutting down dirsrv: 
    M1...[  OK  ]
Starting dirsrv: 
    M1...[  OK  ]

real	0m59.276s
user	0m0.906s
sys	0m0.273s


With 500 replication agreements, it takes less than a minute to restart the server. Hence, marking the bug as Verified.
Comment 10 errata-xmlrpc 2013-02-21 08:17:49 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.

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