Hi, I know there have been a lot of improvements handling flow.xml.gz
differences between nodes if a node get's disconnected or is down. I was
wondering if there is a way to prevent NiFi from allowing any flow changes if
all nodes are not up and available, both on the node that's in a "DISCONNEC
Shawn
So that is one direction (being more restrictive). Another direction
is to simply ditch the logic we have and allow changes and simply
update the disconnected node when it rejoins. We have all kinds of
super complex super duper awesome logic in there to help prevent users
from getting into
than how it used to be.
Thanks
Shawn
-Original Message-
From: Joe Witt
Sent: Thursday, August 26, 2021 10:23 AM
To: users@nifi.apache.org
Subject: Re: Make NiFi Flow Read Only on Disconnect
Shawn
So that is one direction (being more restrictive). Another direction is to
simply ditc
> Shawn
>
> -Original Message-
> From: Joe Witt
> Sent: Thursday, August 26, 2021 10:23 AM
> To: users@nifi.apache.org
> Subject: Re: Make NiFi Flow Read Only on Disconnect
>
> Shawn
>
> So that is one direction (being more restrictive). Another direction is to
&
g cleared and then
> > shutdown and delete flow.xml.gz and restarted. That's already worlds easier
> > than how it used to be.
> >
> > Thanks
> > Shawn
> >
> > -Original Message-----
> > From: Joe Witt
> > Sent: Thursday, August 26, 2021
be.
>>>
>>> Thanks
>>> Shawn
>>>
>>> -Original Message-
>>> From: Joe Witt
>>> Sent: Thursday, August 26, 2021 10:23 AM
>>> To: users@nifi.apache.org
>>> Subject: Re: Make NiFi Flow Read Only on Disconnect
>&
sday, August 26, 2021 10:39 AM
To: users@nifi.apache.org
Subject: Re: Make NiFi Flow Read Only on Disconnect
Bryan,
Those changes only affect when a node starts up, not when it reconnects to a
cluster after startup.
However, there is a Jira [1] that I’m working on currently that should
facilitat