I am running HDF 3.0.1.1 which comes with NiFi 1.2.0.3.0.1.1-5. We are using
SiteToSiteBulletinReportingTask to monitor bulletins (for things like Disk
Usage and Memory Usage). When we restart NiFi via Ambari (either with a Restart
or Stop and then Start), when NiFi comes back up the
SiteToSite
I am standing up 3 new HDF 3.2 clusters (Dev, Cert, and Prod) and we will be
focusing on NiFi (1.7.0) + NiFi Registry (0.2.0). We are using git as our
FlowPersistenceProvider. My plan is to use 1 NiFi Registry (the Prod NiFi
registry) for all 3 clusters, rather than having 3 NiFi Registries and
jf8AyP5Q6Np0yWY19w&r=MJ04HXP0mOz9-J4odYRNRx3ln4A_OnHTjJvmsZOEG64&m=lFWN8OtWhTL6eW3O-K1-lwIDlC0ZViDDrxxFSys2-Lw&s=_4v5XehCxEQZKSAr800935KuCtiECO-BQGkPknz5Gg4&e=
Thanks,
Koji
On Tue, Nov 20, 2018 at 1:38 AM Woodhead, Chad
wrote:
>
> I am stand
seeing nodes
completely disappear from the cluster and not just be in the "disconnected"
state? If so that is a different issue but if they are just "disconnected" you
should be able to see that as the screenshot below illustrates. I am using NiFi
1.8.0 just for ref
t restore on its own.
thanks
On Mon, Dec 10, 2018, 10:08 AM Woodhead, Chad
mailto:chad.woodh...@ncr.com> wrote:
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 st
Q&s=E4jDUra2uIvmsWV4bPBLS5unz_Jl6yUgPvD-ShNcLMI&e=>
On Mon, Dec 10, 2018 at 10:23 AM Joe Witt
mailto:joe.w...@gmail.com>> wrote:
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
My team is about to start using load balanced queues in 1.8 and one thing I
wanted to understand before we do is if we run into this issue and we follow
Dan’s workaround of disconnecting the node and then restarting the node node,
do the flowfiles end up moving through the rest of the flow or do
