[
https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726334#comment-17726334
]
Duong commented on RANGER-4251:
-------------------------------
Thanks for the reply [~madhan].
Yes, we're considering auto-filter to avoid auditing a very large portion of
events. The only problem is Ozone plugin now uses RangerDefaultAuditHandler
which [doesn't
skip|https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java#L91]
auditing even with IsAudited=false.
I'm thinking about having a custom AuditHandler for Ozone, similar to
RangerHiveAuditHandler and other custom ones for HDFS, Hbase..., as per
RANGER-4252. But I think RangerDefaultAuditHandler should be aware of the
IsAudited flag.
> Performance improvement for Ozone plugin
> ----------------------------------------
>
> Key: RANGER-4251
> URL: https://issues.apache.org/jira/browse/RANGER-4251
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Duong
> Priority: Major
> Attachments: image-2023-05-24-15-14-33-403.png,
> ozone-load-test-flamegraph.html, ozone-ranger-flamegraph.png
>
>
> The Ranger plugin for Ozone was implemented as per RANGER-2325.
> When running performance testing on Ozone, we notice that the Ranger plugin
> contributes significantly to Ozone latency and it gets worse when Ozone is
> under heavy load, i.e. 100K OPPS.
> !ozone-ranger-flamegraph.png|width=887,height=265!
> This ticket tracks the effort to improve the performance of the Ranger plugin
> for Ozone.
> Source of inefficiencies identified so far:
> # Ranger is logging/auditing all the requests, including reads that are
> accepted. This is too expensive and will be addressed by RANGER-4252.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
