[
https://issues.apache.org/jira/browse/RANGER-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-3192:
-----------------------------------------
Fix Version/s: 2.2.0
3.0.0
> 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
> Fix For: 3.0.0, 2.2.0
>
>
> 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)
