#47926 change backend code to prevent deadlocks of operations on different backends
Closed: wontfix 3 years ago by mreynolds. Opened 9 years ago by lkrispen.

recently there have been few cases where concurrent writ operations on different backends caused deadlocks or txn abortions because of retry count exceed.

While the operations on one backend are protected by the database backend lock, plugins executed in the context of one of these operations can try to access pages in the database of another backends.

In the cases reported this was resolved by modifying plugin configuration or fixing plugins, but the general deadlock potential still exists.

This is a request to investigate into the change of the backend code together with a potential move away from BDB.


Will be discussed in the early next year 2015.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.4 backlog

7 years ago

Should not be an issue with LMDB, closing

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

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/1257

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata