[
https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725988#comment-17725988
]
Madhan Neethiraj commented on RANGER-4251:
------------------------------------------
[~duongnguyen] - have you considered setting up audit-filters (introduced in
RANGER-3000) for Ozone service? This can be specified via service-config UI.
Here is the screenshot for audit-filter for a Hive service, which skips
auditing of METADATA_OPERATION and SHOW_ROLES operations. Hope this helps.
!image-2023-05-24-15-14-33-403.png|width=1323,height=342!
> 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)
