ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (RANGER-2510) Support for Incremental tag updates to improve performance
Date Tue, 01 Oct 2019 15:22:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938056#comment-16938056
] 

Abhay Kulkarni edited comment on RANGER-2510 at 10/1/19 3:21 PM:
-----------------------------------------------------------------

Commit details:

[https://github.com/apache/ranger/commit/c31d4e45281d18b2f18be315d58dc21ea02c7c47]

 

Additional commit:

[https://github.com/apache/ranger/commit/d484e2bad26cc024e36908691138f8c4ac133f47]


was (Author: abhayk):
Commit details:

[https://github.com/apache/ranger/commit/c31d4e45281d18b2f18be315d58dc21ea02c7c47]

> Support for Incremental tag updates to improve performance
> ----------------------------------------------------------
>
>                 Key: RANGER-2510
>                 URL: https://issues.apache.org/jira/browse/RANGER-2510
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 2.1.0
>
>
> Currently, every change to any tag/service-resource/service-resource->tag mapping causes
complete rebuilding of portions of policy-engine that map accessed resource to their tags.
There are several disadvantages:
> 1. Compute time for rebuilding
> 2. Large traffic from ranger-admin to each of the plugins
> 3. Large load on JVM memory system because of frequent complete rebuilding of portions
of policy-engine.
> It will be more optimal to communicate only the changes to tags and apply them to existing
policy-engine.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message