https://bugs.openldap.org/show_bug.cgi?id=10284
Issue ID: 10284 Summary: RFE: retain subordinate entries to cn=connections,cn=monitor branch for a configurable duration Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs@openldap.org Reporter: chris.paul@rexconsulting.net Target Milestone: ---
Please consider an enhancement to retain entries under the cn=connections,cn=monitor branch for a configurable duration. This would enable monitoring of short-lived connections that currently disappear between polling intervals, significantly increasing the utility of this metric for connection tracking.
https://bugs.openldap.org/show_bug.cgi?id=10284
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX
--- Comment #1 from Howard Chu hyc@openldap.org --- (In reply to chris.paul@rexconsulting.net from comment #0)
Please consider an enhancement to retain entries under the cn=connections,cn=monitor branch for a configurable duration. This would enable monitoring of short-lived connections that currently disappear between polling intervals, significantly increasing the utility of this metric for connection tracking.
Not really feasible in the current design. The entries under cn=connections are created on the fly when a search request comes in, and just walk the list of active connections at that time. There is nowhere in slapd that records of previous connections can be cached. Connection structures are reused by new connections as soon as they're freed by a terminated connection, and accumulating dead connection structures would not only be a memory drain but would also have a major performance impact due to the locking required to manipulate such structures safely.
https://bugs.openldap.org/show_bug.cgi?id=10284
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Keywords|needs_review |