[jira] [Comment Edited] (RANGER-3192) Use read-write locks for managing access to policy-engine and tag-repository

["Abhay Kulkarni (Jira)" <ji...@apache.org>]

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

Abhay Kulkarni edited comment on RANGER-3192 at 3/13/21, 3:08 AM:
------------------------------------------------------------------

Patch is available at the review board:

[https://reviews.apache.org/r/73206/]

 

Additional patch

https://reviews.apache.org/r/73227/


was (Author: abhayk):
Patch is available at the review board:

https://reviews.apache.org/r/73206/

> Use read-write locks for managing access to policy-engine and tag-repository
> ----------------------------------------------------------------------------
>
>                 Key: RANGER-3192
>                 URL: https://issues.apache.org/jira/browse/RANGER-3192
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>
> Use concurrent read-write lock to ensure that access evaluation and policy/tag updates are mutually exclusive in multi-threaded environment
> Ranger uses copy and switch method to handle reads and writes to policy and tag repositories in a multi-threaded environment. Using read/write lock to handle concurrent accesses will save on copy which is more memory and CPU efficient.



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