[jira] [Created] (NIFI-3849) Allow flow/user/authorization configs to be automatically inherited by a node in some cases

["Jeff Storck (JIRA)" <ji...@apache.org>]

Jeff Storck created NIFI-3849:
---------------------------------

             Summary: Allow flow/user/authorization configs to be automatically inherited by a node in some cases
                 Key: NIFI-3849
                 URL: https://issues.apache.org/jira/browse/NIFI-3849
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Core Framework
    Affects Versions: 1.1.1
            Reporter: Jeff Storck
            Priority: Minor


Before a node can join a cluster, it's flow/user/authorizaton config fingerprints much match those of the cluster.  There may be some cases where the node should automatically inherit the flow/user/authorization configs from the cluster even though the fingerprints differ.

Auto-inherit Cases:
* When the connecting node has no data in its flow, but fails the fingerprint comparison with the cluster's flow, most likely it can auto-inherit the cluster flow.  Since no data is currently being processed by the node, changing the flow for that node to make it consistent with the cluster will not have any impact on the processing of data.  However, if a separate flow was created to test something on the disconnected node, those flow additions would be discarded by an auto-inherit process.
* When the connecting node fails user/authorization fingerprint comparisons, most likely it can auto-inherit the user/authorization configs.  If users were added/removed, policies were changed, etc, while the node was disconnected, those changes would be lost by an auto-inherit process. This could also possibly change what is viewable/editable by the current users of the clients that are connected to the node joining the cluster.  Neither of these concerns would have impact on the processing of data on that node.

In these cases, it would prevent the user from having to go to node and deleting the flow/user/authorization configurations from the disk in order to allow the node to connect to the cluster.

It needs to be investigated if auto-inheriting these configurations (if the above cases are met) is preferable to keeping the current behavior of not allowing the node to join if the fingerprints do not match.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)