an add or modify with CSN0 may cause DNA betxnpreop to be called like this:
dna_be_txn_pre_op dna_get_next_value dna_notice_allocation dna_update_shared_config slapi_modify_internal_pb ...
This new op will create a CSN1 > CSN0. This will update the RUV with CSN1. When the DNA betxnpreop completes, the outer operation will update the RUV with CSN0, causing the max CSN in the RUV to go backwards. We can prevent this by moving the DNA code that updates the main database to a betxnpostop.
This is related to https://fedorahosted.org/389/ticket/47392 - it is the betxnpreop RUV update that causes the RUV to become uncached in the outer operation.
wip 0001-Ticket-47418-dna-move-db-updates-to-betxnpostop.patch
We need to allow writes in betxnpreop plugins - there is a better way
Metadata Update from @rmeggins: - Issue assigned to rmeggins - 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/755
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.