[
https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357205#comment-15357205
]
Mark Payne commented on NIFI-1413:
----------------------------------
[~joewitt] with this PR we implement the following logic:
- If a node joins a cluster and has templates not available to the cluster,
those templates are preserved but not shown in the list of templates when
dragging onto the canvas. If the node is restarted as a standalone node, the
template will be made available again.
- If a node joins a cluster and is missing 1 or more templates, it will inherit
the template from the cluster.
- If a node joins a cluster and has a conflicting view of what a template
should look like (this should never happen, as templates are created and are
immutable, but just in case...) then the node assumes the template definition
provided by the cluster.
Does this all seem reasonable to you?
> 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
> Assignee: 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)
