#50906 Improve performance/safety of cn=monitor
Closed: wontfix a year ago by spichugi. Opened 2 years ago by firstyear.

Issue Description

When we view cn=monitor, we call the function in conntable.c connection_table_as_entry. This iterates over the connection table itself while holding the CT lock, rather than using the current connection active list that exists between the CT. This means with a large CT and low connections we may delay on this search.

Additionally, this also means we are holding the CT lock for an extended period which will block connection allocation and deallocation.

We should think about how to improve this structure to unblock this

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.3

2 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/3959

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.