The version was 389-ds-base-1.3.3.9-1 (F21).
A write operation (like a DEL) can update nsuniqueid index. in betxn_postop when it tries to update the changelog/ruv, it tries to update the replica agreements and so acquire the RA locks.
If at the same time, the replica agreement is started, it triggers an internal search to retrieve the current ruv. It does internal search using nsuniqueid and so while it is holding the RA lock it accesses the nsuniqueid index.
Could be related to fix: Ticket 47368 - IPA server dirsrv RUV entry data excluded from replication
How to reproduce: I reproduced it several times on VM F21 with ticket47787_test.py
attachment 48179.tar.gz
I also ran into this deadlock while investigating ticket 47788.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1243950
attachment 0001-Ticket-48179-Starting-a-replica-agreement-can-lead-t.patch
Looks good!
An extremely minor issue. We don't need this cast any more! ;)
705 (Slapi_DN *)repl_sdn,
I rmeoved that cast. Thanks for the review Noriko!
f5d2445..eb3086d master -> master commit eb3086d Author: Mark Reynolds mreynolds@redhat.com Date: Fri Jul 17 15:08:00 2015 -0400
8600a5e..23a3ff6 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit 23a3ff6
Metadata Update from @tbordaz: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.2
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/1510
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: Fixed)
Login to comment on this ticket.