[
https://issues.apache.org/jira/browse/RANGER-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2186:
-----------------------------------------
Fix Version/s: (was: master)
1.2.0
> Increment service-specific policy and tag versions after update transaction
> is committed
> ----------------------------------------------------------------------------------------
>
> Key: RANGER-2186
> URL: https://issues.apache.org/jira/browse/RANGER-2186
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: 2.0.0, 1.2.0
>
>
> Policy updates to different policies within a service, when successful,
> update the service's policy version. If the update transactions are
> concurrent, and executed on different ranger-admin servers (in HA
> configuration), then it is possible that policy-version of the transaction
> that commits later overwrites policy-version of earlier transaction,
> effectively losing track of the first change.
> If policy-version is updated after update to policy is committed, then the
> window of such loss is greatly reduced.
> Similar considerations apply for tag updates.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
