Bug 1031227

Summary:	Reduce lock scope in retro changelog plug-in
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	mreynolds, nhosoi, pspacek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.1.6-12.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 13:24:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nathan Kinder 2013-11-15 23:24:09 UTC

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

Comment 1 Sankar Ramalingam 2013-11-25 17:37:41 UTC

Can this be verified on DS environment?

Comment 2 mreynolds 2013-11-25 20:04:59 UTC

Hi Sankar,

There is nothing to verify or reproduce for this bug.

Comment 4 Sankar Ramalingam 2014-02-13 16:47:51 UTC

Marking the bug as Verified as sanity only. No regression found with the latest builds of 389-ds-base-1.3.1.6-18.

Comment 5 Ludek Smid 2014-06-13 13:24:48 UTC

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.