https://bugs.openldap.org/show_bug.cgi?id=10193
Issue ID: 10193 Summary: Asyncmeta starts more than one timeout loop per database Product: OpenLDAP Version: 2.6.7 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: backends Assignee: bugs@openldap.org Reporter: nivanova@symas.com Target Milestone: ---
By design, there should be always exactly one timeout loop task per database, it is a balance to make sure timeout checks do not throttle traffic processing. For some reason, there seems to be more than one. This is only visible if slapd is started with -dasyncmeta log level.
https://bugs.openldap.org/show_bug.cgi?id=10193
Nadezhda Ivanova nivanova@symas.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Asyncmeta starts more than |Asyncmeta starts more than |one timeout loop per |one timeout loop per |database |database and slaptest | |crashes
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.5.18 Keywords|needs_review |
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |IN_PROGRESS
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- https://git.openldap.org/openldap/openldap/-/merge_requests/697
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED
--- Comment #2 from Quanah Gibson-Mount quanah@openldap.org --- head:
• 729a6041 by Nadezhda Ivanova at 2024-04-11T15:26:15+03:00 ITS#10193 Asyncmeta starts more than one timeout loop per database and slaptest crashes
RE26:
• e9c93fac by Nadezhda Ivanova at 2024-04-16T15:45:51+00:00 ITS#10193 Asyncmeta starts more than one timeout loop per database and slaptest crashes
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CONFIRMED Resolution|FIXED |---
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS
--- Comment #3 from Quanah Gibson-Mount quanah@openldap.org --- Nadya,
The current code does not apply to RE25, can you please open a PR for that, or if it's not feasible, let me know so we can adjust the target.
https://bugs.openldap.org/show_bug.cgi?id=10193
--- Comment #4 from Nadezhda Ivanova nivanova@symas.com --- Hi Quanah, This, and the fix for 10197 which is in progress, depend on 6463280d8cbfcbcd67ea25501820fbde877e3685, which does not seem to be included in 2.5. I am not sure how to change the target release, but I don't think it makes sense to include these in anything older than 2.6.6.
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.5.18 |2.6.8 Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED
--- Comment #5 from Quanah Gibson-Mount quanah@openldap.org --- (In reply to Nadezhda Ivanova from comment #4)
Hi Quanah, This, and the fix for 10197 which is in progress, depend on 6463280d8cbfcbcd67ea25501820fbde877e3685, which does not seem to be included in 2.5. I am not sure how to change the target release, but I don't think it makes sense to include these in anything older than 2.6.6.
Great, ty!
https://bugs.openldap.org/show_bug.cgi?id=10193
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED