Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1044141 - MMR stress test with dna enabled causes a deadlock
MMR stress test with dna enabled causes a deadlock
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.0
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
Viktor Ashirov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-17 16:20 EST by Nathan Kinder
Modified: 2015-03-05 04:30 EST (History)
1 user (show)

See Also:
Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 04:30:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0416 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 09:26:33 EST

  None (edit)
Description Nathan Kinder 2013-12-17 16:20:20 EST
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47400

Steps
1. set up 2way MMR (master/1.3.2 build)
2. enable DNA on both masters
3. Repeat add and delete users from 10 clients
   The server hangs in an hour for me.
Comment 2 Sankar Ramalingam 2015-01-14 07:35:59 EST
Executed DNA acceptance tests without cleanup tests.
Then, on the same DNA MMR setup, added/deleted 100,000 users to both M1 and M2.
Waited for more than an hour to see itf there are crashes.No crashes reported, no issues related performance and memory.

Hence, marking the bug as Verified.
Comment 5 errata-xmlrpc 2015-03-05 04:30:05 EST
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-2015-0416.html

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