[
https://issues.apache.org/jira/browse/HDDS-13794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031307#comment-18031307
]
Ivan Andika commented on HDDS-13794:
------------------------------------
Note that for OM, synchronously logging the OM request might potentially block
the OM Ratis OzoneManagerStateMachine#applyTransaction and can cause
performance regression. Therefore, we need to either:
* Move the audit logs out of the validateAndUpdateCache
** We can potentially move it to OMExecutionFlow#submitExecutionToRatis (after
submitting the OM request to Ratis)
* Use a flag to enable the synchronized logger (disabled by default)
> Use synchronized logger for auditing tasks
> ------------------------------------------
>
> Key: HDDS-13794
> URL: https://issues.apache.org/jira/browse/HDDS-13794
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Rishabh Patel
> Assignee: Rishabh Patel
> Priority: Major
>
> Currently, we use the Async Logger to perform all logging activities.
> When under stress, Async Logger
> [drops|https://logging.apache.org/log4j/2.x/manual/async.html#log4j2.asyncLoggerRingBufferSize]
> events that were supposed to be logged.
> This results in incomplete audit logs.
> Furthermore, as per the Log4J documentation Async Logger should not be used
> for auditing purposes.
> ??If logging is part of your business logic, e.g. you are using Log4j as an
> audit logging framework, we would recommend to synchronously log those audit
> messages.??
> [https://logging.apache.org/log4j/2.x/manual/async.html#async-drawbacks]
> The goal of this task is to transition to a synchronized logger for auditing
> activities.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
