Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1332
I have a question about this process (may be beyond the scope of this PR
though) -- why not allow the DFM to remove the flow.xml.gz from the node with
outdated flow via the REST API and UI from any connected node? The issue is not
limited or blocked connectivity between the nodes, so there could be logic on
the node itself to remove its flow definition when given a properly-authorized
command from a remote node that it knows is connected to the cluster. The
authentication should not be an issue as the DFM permissions should be the same
across the cluster.
I at first considered allowing the node to perform this logic on its own by
archiving its current flow and then deleting it to attempt to rejoin the
cluster, but I can understand how admins would be uncomfortable that the level
of autonomous activity could lead to data loss.
Thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
