[
https://issues.apache.org/jira/browse/NIFI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907278#comment-14907278
]
Mark Payne commented on NIFI-48:
--------------------------------
We've also had people reporting bad error messages when templates are different
on node than NCM. The error reports that the flows are different, rather than
indicating that the templates are different. From the users mailing list:
Hi,
I created a 2 node cluster but I was having development issues so I worked with
only one until I got a custom processor working. I attempted to add the second
node back in but get the error "Failed to connect node to cluster because local
flow is different than cluster flow.” I deleted the flow.xml.gz file from the
node I’m attempting to add, then restarted, same issue. I even copied the
flow.xml.gz file from node 1 to node 2, same issue.
Any ideas?
Thanks,
-jeff
> Startup failures should be more graceful/user friendly
> ------------------------------------------------------
>
> Key: NIFI-48
> URL: https://issues.apache.org/jira/browse/NIFI-48
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Joseph Witt
> Fix For: 0.4.0
>
>
> Many startup issues result in massive strack traces and things which will
> make users have to work much harder than necessary to see the real problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
