[
https://issues.apache.org/jira/browse/RANGER-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429110#comment-17429110
]
Xuze Yang commented on RANGER-3472:
-----------------------------------
[~madhan]
In my understanding, high-availability means failover. Just like in hdfs, under
normal circumstances, Active NameNode provides services to the outside world.
When Active NameNode crash down, the Standby NameNode will transition to Active
NameNode and take over everything. i.e. At the same time, only one instance
will provide services. So we needn't consider the multiple instances scenario.
I don’t know whether the ha of ranger is consistent with the ha of hdfs,
because I haven’t found a design document about the ranger ha. Can you give
more details，or can you push the design docs to me. thanks!
> The createPolicy() method is not thread safe. In another word, we can create
> policies with same resources when creating policies concurrently
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-3472
> URL: https://issues.apache.org/jira/browse/RANGER-3472
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.1.0
> Reporter: Xuze Yang
> Priority: Major
>
> In our production environment, we happen to find that two policies exist with
> the same resources.In this case, when we want to modify either policy, ranger
> doesn't allow this operation and throws message like "*Error Code : 3010
> Another policy already exists for matching resource: policy-name=[hhh9],
> service=[default-Hdfs]*".
> I go through the source code about create policy, find that the
> createPolicy() in class ServiceREST is not thread safe. When we create
> policies concurrently, we may create several policies with the same resources.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
