https://bugs.openldap.org/show_bug.cgi?id=9886
Issue ID: 9886 Summary: At "sync" logging, nothing shows how long a write op took on consumers Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs@openldap.org Reporter: quanah@openldap.org Target Milestone: ---
If sync logging is enabled on a consumer, there's no etime logged which means it is not possible to see how long a write op took on that consumer. This can be useful information to see how the node is performing, particularly if it is a read only node where there will be no general MOD timing logged.
https://bugs.openldap.org/show_bug.cgi?id=9886
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Target Milestone|--- |2.7.0
https://bugs.openldap.org/show_bug.cgi?id=9886
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- head:
• 9134be7e by Ondřej Kuzník at 2022-09-26T16:37:14+00:00 ITS#9886 Maintain si_lastcontact as struct timeval
• 14820483 by Ondřej Kuzník at 2022-09-26T16:37:14+00:00 ITS#9886 Report time taken to process each syncrepl message
https://bugs.openldap.org/show_bug.cgi?id=9886
--- Comment #2 from Ondřej Kuzník ondra@mistotebe.net --- *** Issue 8673 has been marked as a duplicate of this issue. ***
https://bugs.openldap.org/show_bug.cgi?id=9886
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nivanova@symas.com
--- Comment #3 from Quanah Gibson-Mount quanah@openldap.org --- *** Issue 10293 has been marked as a duplicate of this issue. ***