nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Bean <mark.o.b...@gmail.com>
Subject Re: List/Empty queue on a Cluster
Date Mon, 20 Mar 2017 19:53:12 GMT
I observed that only the Cluster Coordinator Node (which also happens to be
the Primary Node) needed to be on the Access Policy, not all Nodes.

More to the point, why do the Node(s) themselves need to be on the policy?
When not Clustered, the machine does not need to be on the policy. Perhaps
this is necessary in a Cluster because one Node propagates the request the
remaining Nodes.. so it is the Node making the request, not the individual
User?

Looking for clarification.

Thanks,
Mark


On Mon, Mar 20, 2017 at 3:45 PM, Arpit Gupta <arpit@hortonworks.com> wrote:

> Hi Mark
>
> One needs to make sure all nodes in your cluster are added to the policy
> and not just the cluster coordinator.
>
> --
> Arpit
>
> On Mar 20, 2017, at 12:05 PM, Mark Bean <mark.o.bean@gmail.com<mailto:
> mark.o.bean@gmail.com>> wrote:
>
> In order to successfully 'List queue', a user must be part of the 'view the
> data' access policy. Similarly, in order to successfully 'Empty queue', a
> user must be part of the 'modify the data'. However, in a Cluster
> configuration, it appears the Cluster Coordinator must also be in the
> relevant policy in order to be successful.
>
> Is this expected behavior?
>
> Apache NiFi 1.1.2
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message