You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Farrukh Bhatti (Jira)" <ji...@apache.org> on 2020/09/28 10:50:00 UTC
[jira] [Commented] (NIFI-5866) Cluster gets out of sync: "X is not
the most up-to-date revision."
[ https://issues.apache.org/jira/browse/NIFI-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203149#comment-17203149 ]
Farrukh Bhatti commented on NIFI-5866:
--------------------------------------
Hello,
I am facing the same issue in Nifi version 1.11.4 in our production cluster where above workaround is not possible. I have one ExecuteGroovyScript processor while
performing anything on it I am facing the below issue
!nifi-error.PNG!
> Cluster gets out of sync: "X is not the most up-to-date revision."
> ------------------------------------------------------------------
>
> Key: NIFI-5866
> URL: https://issues.apache.org/jira/browse/NIFI-5866
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: CentOS 6.9, NiFi 1.6.0 cluster of 4, running on AWS EC2 VMs.
> Reporter: Joseph Gresock
> Priority: Major
> Attachments: Error.png, nifi-error.PNG, nifi-image.PNG
>
>
> Since upgrading to 1.6.0, I have started to see this error sometimes when I try to modify a component (start, stop, configure, move, etc.):
>
> Node X is unable to fulfill this request due to: [12, <some uuid>, <some uuid>] is not the most up-to-date revision. This component appears to have been modified.
>
> The only way I have found to resolve this is to disconnect and then delete the node from the cluster, then try again, repeating the process until the flow can be modified. Afterwards, I have to stop nifi on the disconnected nodes, delete their flow.xml.gz, and let them rejoin the cluster with a fresh copy of the flow.
>
> This sometimes happens multiple times per day.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)