yandrey321 commented on code in PR #9264: URL: https://github.com/apache/ozone/pull/9264#discussion_r2511438044
########## hadoop-hdds/docs/content/design/logger-benchmark.md: ########## @@ -0,0 +1,64 @@ +--- +title: Audit Logger Benchmarks +summary: Benchmarking the async and sync audit loggers using log4j2 +date: 2025-11-02 +jira: HDDS-13894 +status: implemented +author: Rishabh Patel +--- +<!-- + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. See accompanying LICENSE file. +--> +## Introduction & Goal + +This document presents the performance benchmark results comparing our current Asynchronous (Async) Logger with +a new Synchronous (Sync) Logger configuration in Log4j2. +The primary goal of this testing is to validate the performance impact of transitioning our audit logging framework +to a Sync Logger. +This transition is critical to guarantee the integrity and completeness of our audit logs, as the current Async Logger +can drop log events under high stress. + + +## Benchmark Methodology +To evaluate the impact, we ran a series of tests using the ozone freon tool to simulate the OM being under pressure. + +- We used a bare-metal cluster with a few configuration tweaks to perform these tests. + +- The OM log directory was moved from an SSD to an HDD to expose any issues when the disk is slow. Review Comment: what is our typical destination for audit logs? Do we put logs to the system drive? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
