Red Hat Bugzilla – Bug 830348
Slow shutdown when you have 100+ replication agreements
Last modified: 2013-02-21 03:17:49 EST
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.
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.
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.
Please add steps to verify Is it possible to verify this bugzilla without 150 replicas?
Mark, did you check in a TET test for this issue?
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.
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.
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