Purushotham,
If the node is disconnected and then attempts to reconnect, flow election does
not occur. Rather, the node obtains a copy of the flow
from the cluster, determines whether or not it matches, and if so rejoins. If
the flow does not match, it disconnects and stops trying to
reconnect.
I agree with 786 for sure. I apologize, I may have interpreted your
initial response a bit literally with regards to the "feature bearing"
JIRAs. Just wanted to clarify that new features would not be in scope for
a fix version release, but in terms of adjusting the expected
functionality, totally
Completely agree but isn’t MINIFICPP-786 an issue we could include as part
of that?
On Wed, Jun 26, 2019 at 6:35 PM Aldrin Piri wrote:
> I think the intent is for this to be a fix release and wouldn’t include
> any new features.
>
> > On Jun 26, 2019, at 17:47, Jeremy Dyer wrote:
> >
> > +1 it’
Hi,
I'm having a 3 nodes( ver 1.9.2) cluster running in production. As infra is
unreliable due to various factors, our nodes go down often. We don't have
distinction between dev and prod cluster. We modify, deploy, test in the
same cluster. However, when one of the node goes down NiFi restricts us
