You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Abhay Kulkarni (JIRA)" <ji...@apache.org> on 2018/08/10 00:54:00 UTC

[jira] [Created] (RANGER-2186) Increment service-specific policy and tag versions after update transaction is committed

Abhay Kulkarni created RANGER-2186:
--------------------------------------

             Summary: 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
             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)