389-ds-base

#51202 Issue 51000 - Separate the BDB backend monitors
Closed by spichugi. Opened by mreynolds.
mreynolds/389-ds-base issue51000  into  master

Download 51202.patch

Bug Description:

While trying to remove duplicate code from the backend and BDB backend code, I found that we were not correctly separating the BDB monitors from the core backend code.

Fix Description:

Move all the monitor registering to the db_layer private structure. This way we have fully isolated the monitors for each backend implementation/library. This also removed some duplicate code from the core backend and BDB code.

relates: https://pagure.io/389-ds-base/issue/51000

The code LGTM!
Also, basic, replication, import and disk_monitoring test suites pass.

rebased onto ed5b13cab68f82ae6a1abe03bf41eb7369c30f2c

Pull-Request has been merged by mreynolds

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/4255

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.