[
https://issues.apache.org/jira/browse/RANGER-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726338#comment-17726338
]
Madhan Neethiraj commented on RANGER-4251:
------------------------------------------
{quote}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
{quote}
[~duongnguyen] - when result.isAudited is set to false,
RangerDefaultAuditHandler doesn't generate audit - see
[here|https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java#L112].
A custom audit handler shouldn't be necessary for this.
> 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 quite expensive and involves lock contention (internally in
> LinkedBlockingQueue) and thus does not scale well for hundred thousands TPS.
> It will be addressed by RANGER-4252.
> # RangerPolicyEngineImpl spends most of its time looking for matching
> evaluators for requests, aka
> "policyRepository.getLikelyMatchPolicyEvaluators(request, policyType);". This
> contains list creation, filter, and sorting so is not cheap. We should check
> if it's catchable or optimizable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
