change backend code to prevent deadlocks of operations on different backends

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47926

• Created at 2014-10-15 17:00:51 by lkrispen (@elkris)
• Closed at 2020-05-20 16:54:22 as wontfix
• Assigned to nobody

---

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.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-11-11 04:18:43

Will be discussed in the early next year 2015.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 23:10:31

Metadata Update from @nhosoi:

• Issue set to the milestone: 1.4 backlog

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-05-20 16:54:23

Should not be an issue with LMDB, closing

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-05-20 16:54:24

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None
• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)