Skip to main content
fy-test
fy-test
Silver ⭐️⭐️
February 12, 2025
Solved

Resync action - nifi 1.24

Hi, 

We are running nifi 1.24, some times when developers apply the changes it causes a discount for one of the nodes, and it is unable to sync with the other nodes.

How can I have a re-sync button to re-sync the flows, to avoid the need to delete the flow directly from the affected node?

MattWho
MattWhoAnswer
Titanium ⭐️⭐️⭐️
February 12, 2025

@fy-test 

The NiFi node that disconnects due to a flow mismatch should inherit the cluster flow when it attempts to rejoin the cluster.  The only time this is not possible is if the cluster flow includes change that would result in dataloss.

Example:
Cluster flow has a connection removed that on the connecting node still has queued FlowFiles.

NiFi has not feature to force removal/archive of a flow.json.gz on a disconnected node.
You could file an Apache NiFi improvement jira here:
https://issues.apache.org/jira/projects/NIFI

But first step is to identify why your node is not able to inherit cluster flow and rejoin the cluster.  What is the exception logged when it attempts to rejoin the cluster?

Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

View in thread

2 replies

DianaTorres
Community Manager
DianaTorres
Community Manager
February 12, 2025

@fy-test Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our NiFi experts @mburgess @MattWho  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

Translate
Regards, Diana Torres, Senior Community Moderator
MattWho
Titanium ⭐️⭐️⭐️
MattWhoAnswer
Titanium ⭐️⭐️⭐️
February 12, 2025

@fy-test 

The NiFi node that disconnects due to a flow mismatch should inherit the cluster flow when it attempts to rejoin the cluster.  The only time this is not possible is if the cluster flow includes change that would result in dataloss.

Example:
Cluster flow has a connection removed that on the connecting node still has queued FlowFiles.

NiFi has not feature to force removal/archive of a flow.json.gz on a disconnected node.
You could file an Apache NiFi improvement jira here:
https://issues.apache.org/jira/projects/NIFI

But first step is to identify why your node is not able to inherit cluster flow and rejoin the cluster.  What is the exception logged when it attempts to rejoin the cluster?

Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

Translate
Terms & ConditionsAccessibility statement