[
https://issues.apache.org/jira/browse/RANGER-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292180#comment-17292180
]
Abhay Kulkarni edited comment on RANGER-3192 at 3/13/21, 3:09 AM:
------------------------------------------------------------------
Commit details:
master:
[https://github.com/apache/ranger/commit/b69c2df7625696b3d38cf1cfbbcf1db4d634c7b0]
ranger-2.2:
[https://github.com/apache/ranger/commit/c20d0e0a65aed8f7fbd8020acfe1612c9b7887f8]
Additional commit:
master:
[https://github.com/apache/ranger/commit/4a6b9d19870bd3a272fa86d005899530f7cdf739]
ranger-2.2:
[https://github.com/apache/ranger/commit/30836f8def9a7cf8eeac1e0cf13634edf3a243ea]
was (Author: abhayk):
Commit details:
master:
[https://github.com/apache/ranger/commit/b69c2df7625696b3d38cf1cfbbcf1db4d634c7b0]
ranger-2.2:
[https://github.com/apache/ranger/commit/c20d0e0a65aed8f7fbd8020acfe1612c9b7887f8]
> 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)
