[
https://issues.apache.org/jira/browse/RANGER-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581927#comment-16581927
]
Abhay Kulkarni edited comment on RANGER-2186 at 9/17/18 6:43 PM:
-----------------------------------------------------------------
Commit details:
master:
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=3aa94596be73371a64f190ef6e01ab93d6ef8e78]
master:
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=9f639f3c5876c7134f43df33467691a2b01735a7
was (Author: abhayk):
Commit details:
master:
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=3aa94596be73371a64f190ef6e01ab93d6ef8e78
> 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: master
>
>
> 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)
