[
https://issues.apache.org/jira/browse/NIFI-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Lachterman updated NIFI-4555:
---------------------------------
Attachment: NiFI NAR issues
nifi-fails-to-start.log
Stack traces and chat logs
> Improve error messaging when missing components in flow definition during
> cluster copy
> --------------------------------------------------------------------------------------
>
> Key: NIFI-4555
> URL: https://issues.apache.org/jira/browse/NIFI-4555
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.4.0
> Reporter: Andy LoPresto
> Labels: component-versioning, error, stacktrace, startup
> Attachments: NiFI NAR issues, nifi-fails-to-start.log
>
>
> I recently diagnosed an issue where a user copied a {{flow.xml.gz}} file from
> one NiFi instance to another and the destination node failed to start. We
> determined that the origin node had custom NARs loaded containing components
> that did not exist on the destination node. The error messaging in the
> {{nifi-app.log}} file was not helpful for determining this issue.
> I propose improving the error message to be much clearer about what is
> happening and what specific components are missing, and possibly bringing up
> the UI with "ghosted" components displayed in the UI (and the flow
> unavailable to be started until that is resolved).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
