nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Villard (Jira)" <>
Subject [jira] [Commented] (NIFI-7246) JWT Generated by a node in the cluster is not honored by other nodes in the cluster.
Date Sun, 15 Mar 2020 13:48:00 GMT


Pierre Villard commented on NIFI-7246:

Creating flows does not require a lot of API calls. Besides when you make a call on one node,
the call is replicated on the other nodes (for most of the APIs at least). This would not
change anything in terms of load repartition across the nodes. And that would be exactly the
same if using the UI to create the flows.

I don't see any scenario where a node would be overwhelmed by API calls. It's the same for
monitoring: when calling a monitoring API, the node receiving the request will make the same
request to the other nodes to aggregate the cluster status. Besides... if you think that the
monitoring of NiFi is going to create pressure on the NiFi node itself, I'd seriously challenge
the way NiFi is monitored. Reporting task to push metrics out of NiFi would be a better approach.

I've seen automation through API calls in many places where NiFi is used heavily and session
stickiness has never been an issue. If you have a scenario where it creates resources contention,
please share more details.

> JWT Generated by a node in the cluster is not honored by other nodes in the cluster.
> ------------------------------------------------------------------------------------
>                 Key: NIFI-7246
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Security
>            Reporter: Shreyas KC
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
> In an externally load balanced cluster without sticky session, it is not possible to
currently share the JWT generated by one node with the rest of the nodes in the cluster.
> Hence we need a mechanism where we can introduce static key in the in
its chosen by the cluster administrator.

This message was sent by Atlassian Jira

View raw message