Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/47599 Looks like the locking in the retro changelog code is too big - write_replog_db - the retrocl_internal_lock lock scope is very large. Or perhaps even get rid of locking and use atomics. We are seeing deadlock issues related to this as described in the following FreeIPA ticket: https://fedorahosted.org/freeipa/ticket/3967
Can this be verified on DS environment?
Hi Sankar, There is nothing to verify or reproduce for this bug.
Marking the bug as Verified as sanity only. No regression found with the latest builds of 389-ds-base-1.3.1.6-18.
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.