chad
there have been a ton of improvements overall. but the causes of
disconnects are much better handled and largely resolved. for cases that
remain due to general distrubuted systems fun auto join is better.
so def happy to hear your findings with 1.8
thanks
On Mon, Dec 10, 2018, 10:48 AM
Joe,
Our current dev/cert/prod flows run on NiFi 1.2.0 and this is where we face
this issue a lot (hence why we created the first version of the monitoring
flow). We have stood up new clusters which are running NiFi 1.8.0. No
users/flows are running on the new 1.8.0 clusters besides our Admin
Chad - Ahh I see what you are saying now. To Joe's point the problems
really shouldn't be there anymore. However to resolve what you are seeing
the best practice is to setup the cluster behind a reverse proxy [1]. In
this configuration you are not accessing the REST API on an explicit node
and the
chad
in 1.8.0 you should not see much need to script that. are you still seeing
disconnects in 1.8.0 that it doesnt restore on its own.
thanks
On Mon, Dec 10, 2018, 10:08 AM Woodhead, Chad Hey Jeremy!
>
>
>
> We occasionally see a node disconnect from the cluster (not disappear from
> the
Hey Jeremy!
We occasionally see a node disconnect from the cluster (not disappear from the
cluster) so I’m building this flow just to reconnect a disconnected node. The
cluster still shows the node, but just that it is in a disconnected state.
As far as the API call to
