[jira] [Resolved] (NIFI-5866) Cluster gets out of sync: "X is not the most up-to-date revision."

["Mark Payne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne resolved NIFI-5866.
------------------------------
    Fix Version/s: 1.13.0
       Resolution: Duplicate

This is a duplicate of NIFI-7920, which was fixed in 1.13.0. While NIFI-7920 calls out Controller Services specifically, it could happen for other components as well.

> 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
>             Fix For: 1.13.0
>
>         Attachments: Error.png, nifi-error.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)