Background info: On 06/25/2013 04:30 AM, Rich Megginson wrote:
One of the main reasons we used to have no locking for OP_FLAG_REPL_FIXUP was because we used a simple mutex for the backend lock and it was not re-entrant. So when an URP op had to do a recursive db call it would block because the outer op had already locked the db. Since we now use a PR_Monitor instead of a mutex, it is re-entrant, and I wonder if we can just get rid of all of the !operation_is_flag_set(operation,OP_FLAG_REPL_FIXUP) checks before locking the seriallock.
It is already taken care in 1.3.0 and newer.
Metadata Update from @nhosoi: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/744
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.