[
https://issues.apache.org/jira/browse/RANGER-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707783#comment-17707783
]
Madhan Neethiraj commented on RANGER-4170:
------------------------------------------
[~ximz] - can you update the Jira with the version of Ranger this issue was
seen in? There were few fixes related to cache in 2.2.0/2.3.0 releases:
RANGER-3343, RANGER-3253, RANGER-3371, RANGER-3554.
> keep policy-cache snapshot for each update
> ------------------------------------------
>
> Key: RANGER-4170
> URL: https://issues.apache.org/jira/browse/RANGER-4170
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Xiaomin Zhang
> Priority: Major
>
> We observed strange issue that plugin is not able to find the correct policy
> hence failing the access request. This is intermittent and not reproduced at
> will. This issue seems gone after restarting the component or RangerAdmin or
> make some slight changes to the affected policy, or just wait for some while
> without doing any thing.
> Since policy-cache snapshot at the issue time is critical to debug this
> issue, but there is a major gap here to keep the snapshot. We need some
> improvement in component plugin to keep every policy-cache snapshot when it's
> updated, so that we can trace back to find the policy-cache at the point of
> time when issue recurs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
