dles this; but that it's complicated. I can believe hat.
> >
> > But, in the meantime, there probably isn't a problem with exposing this
> > piece of scheduling information in the ProcessContext?
> >
> > Thanks,
> > Peter
> >
> > -Original Message--
> Thanks,
> Peter
>
> -Original Message-
> From: Bryan Bende
> Sent: Friday, August 16, 2019 9:19 AM
> To: dev@nifi.apache.org
> Subject: [EXT] Re: OnPrimaryNodeStateChange vs Primary Only configuration
>
> AbstractSessionFactoryProcessor has a method
&g
-
From: Bryan Bende
Sent: Friday, August 16, 2019 9:19 AM
To: dev@nifi.apache.org
Subject: [EXT] Re: OnPrimaryNodeStateChange vs Primary Only configuration
AbstractSessionFactoryProcessor has a method
getNodeTypeProvider().isPrimary()
The ultimate fix for your problem is that a processor shouldn't
AbstractSessionFactoryProcessor has a method
getNodeTypeProvider().isPrimary()
The ultimate fix for your problem is that a processor shouldn't have
it's onScheduled called at all unless it is actually schedule to run
on that node. Currently it calls onScheduled on all nodes, but then
never calls
I'm working on a bug fix for HandleHttpRequest and need to check if a processor
is configured to run only on primary node (and not if a processor has the
attribute that ONLY allows it to run on primary node).
Here is the scenario for background:
* NiFi cluster, but all nodes are on the same
