[jira] [Updated] (NIFI-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.

["Matt Burgess (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-1413:
-------------------------------
    Resolution: Fixed
      Assignee:     (was: Mark Payne)
        Status: Resolved  (was: Patch Available)

> NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.
> ------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1413
>                 URL: https://issues.apache.org/jira/browse/NIFI-1413
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> If a node tries to join a cluster, the node will fail to join and a notification will indicate that the flow on the node is different than the cluster's flow, just because the templates are different.
> Rather, we should rename the old template to "<original name>.standalone" or something of that nature and then write the template to a new file if it conflicts. If the template is simply missing, it should just be downloaded.
> We should make sure that NCM lists only those templates that are available to it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)