[
https://issues.apache.org/jira/browse/RANGER-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated RANGER-2878:
-------------------------
Description:
Current incremental policy update mechanism may cause issues in two cases.
1. When policy is updated, it is consist of two operations: delete then
add. Policy is temporarily unavailable after delete operation and before add
operation. It may cause task failure.
2. RangerResourceTrie is also updated when matching policies (ref
RANGER-2760 and RANGER-2761). Without read write lock, it will lead to chaos
and inaccurate result.
was:
Current incremental policy update mechanism may cause issues in two cases.
1. When policy is updated, it is consist of two operations: delete then
add. Policy is temporarily unavailable after delete and before add operation.
It may cause task failure.
2. RangerResourceTrie is also updated when matching policies (ref
RANGER-2760 and RANGER-2761). Without read write lock, it will lead to chaos
and inaccurate result.
> Add read write lock to RangerResourceTrie
> -----------------------------------------
>
> Key: RANGER-2878
> URL: https://issues.apache.org/jira/browse/RANGER-2878
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 2.0.0
> Reporter: star
> Assignee: star
> Priority: Major
>
> Current incremental policy update mechanism may cause issues in two cases.
> 1. When policy is updated, it is consist of two operations: delete then
> add. Policy is temporarily unavailable after delete operation and before add
> operation. It may cause task failure.
> 2. RangerResourceTrie is also updated when matching policies (ref
> RANGER-2760 and RANGER-2761). Without read write lock, it will lead to chaos
> and inaccurate result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
