[
https://issues.apache.org/jira/browse/NIFI-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227803#comment-16227803
]
Sam Lachterman commented on NIFI-4555:
--------------------------------------
In addition to the described behavior, I also wanted to note the behavior when
not copying the flow.xml.gz to the new node:
The flow.xml.gz that got created at startup was practically empty, it only
contained controller services metadata. It appears that the inherited flow was
corrupted in some way by the non-existence of the NARs on the new node.
It was required to manually copy the flow.xml.gz file to the new node in order
to get the more detailed debugging information:
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed
Flow is not inheritable by the flow controller because of differences in
missing components: Proposed flow has missing components that are not
considered missing in the current flow
(c7f897a1-015a-1000-af5b-36cbe5d33696,c8018620-015a-1000-a571-20e9d8ef4976,c7fdf9a9-015a-1000-9c22-4b680412ec08,c7fadce0-015a-1000-881e-e6cc89672b1e,80c3ab73-015d-1000-ffff-ffffa91c652d,7029b9ee-015a-1000-9f16-9bf58179e5b3,c7f92bbb-015a-1000-91a5-dc2883dc54cc,c8004522-015a-1000-9bb5-c6e68de6f07c,c7f92bbb-015a-1000-96a2-a1250c7b74c4)
> 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)
