The version was 389-ds-base-22.214.171.124-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
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
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
Author: Mark Reynolds firstname.lastname@example.org
Date: Fri Jul 17 15:08:00 2015 -0400
8600a5e..23a3ff6 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
Metadata Update from @tbordaz:
- Issue assigned to mreynolds
- Issue set to the milestone: 126.96.36.199
to comment on this ticket.