Based on the design http://www.port389.org/docs/389ds/design/logging-performance-improvement.html we should make the log system have buffering, async write and potentially double-buffer to prevent holding the mutex for too long,
In this change, we should probably gut and replace most of the log interior as we duplicate a large quantity of code in the log.c file. When we make this change we must add support for errors and audit to be buffered also, and also a tool to allow gdb/core dumping of in memory log events,
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4 backlog
Raising priority on this, due to a large number of issues that could have been resolved if logging was more performant, allowing debbuging to be enabled.
Metadata Update from @firstyear: - Issue priority set to: major
https://pagure.io/389-ds-base/issue/49260 <<-- update log timestamp
Metadata Update from @firstyear: - Issue assigned to firstyear
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/2474
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
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)
Login to comment on this ticket.