All processors stopped on startup

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

All processors stopped on startup

Joe Gresock
I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all
processors are stopped on startup.  However, the flow.xml.gz on disk
appears to have the correct scheduledState values.  I'm afraid to touch the
flow in the UI, lest it save all 500 of my processors as stopped.

Is there anything new in 1.2.0 that would cause this?

--
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.    *-Philippians 4:12-13*
Reply | Threaded
Open this post in threaded view
|

Re: All processors stopped on startup

Joe Gresock
One more key observation.. it actually appears that the processors are
running, even though their icons show that they are stopped.  For example,
the tasks/time keeps going up even though a GetSQS processor looks
stopped.  However, the fact that they appear stopped also seems to be
confusing the UI, which prevents me from starting any processors that
happen to have a thread running.

On Fri, May 12, 2017 at 4:08 PM, Joe Gresock <[hidden email]> wrote:

> I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all
> processors are stopped on startup.  However, the flow.xml.gz on disk
> appears to have the correct scheduledState values.  I'm afraid to touch the
> flow in the UI, lest it save all 500 of my processors as stopped.
>
> Is there anything new in 1.2.0 that would cause this?
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can
> do all this through him who gives me strength.    *-Philippians 4:12-13*
>



--
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.    *-Philippians 4:12-13*
Reply | Threaded
Open this post in threaded view
|

Re: All processors stopped on startup

Tim Reardon
I too have encountered all processors being stopped after restarting 1.2.0.
(I am running a single node.) This happened several times, but on at least
one occasion they remained running. I am pretty sure that in my case when
the UI showed them stopped they really were stopped, and not running
surreptitiously.

On Fri, May 12, 2017 at 12:10 PM, Joe Gresock <[hidden email]> wrote:

> One more key observation.. it actually appears that the processors are
> running, even though their icons show that they are stopped.  For example,
> the tasks/time keeps going up even though a GetSQS processor looks
> stopped.  However, the fact that they appear stopped also seems to be
> confusing the UI, which prevents me from starting any processors that
> happen to have a thread running.
>
> On Fri, May 12, 2017 at 4:08 PM, Joe Gresock <[hidden email]> wrote:
>
> > I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all
> > processors are stopped on startup.  However, the flow.xml.gz on disk
> > appears to have the correct scheduledState values.  I'm afraid to touch
> the
> > flow in the UI, lest it save all 500 of my processors as stopped.
> >
> > Is there anything new in 1.2.0 that would cause this?
> >
> > --
> > I know what it is to be in need, and I know what it is to have plenty.  I
> > have learned the secret of being content in any and every situation,
> > whether well fed or hungry, whether living in plenty or in want.  I can
> > do all this through him who gives me strength.    *-Philippians 4:12-13*
> >
>
>
>
> --
> I know what it is to be in need, and I know what it is to have plenty.  I
> have learned the secret of being content in any and every situation,
> whether well fed or hungry, whether living in plenty or in want.  I can do
> all this through him who gives me strength.    *-Philippians 4:12-13*
>
Reply | Threaded
Open this post in threaded view
|

Re: All processors stopped on startup

Joe Gresock
So, this may be related to how the cluster propagates the flow.xml.gz.  I
noticed that when I cleared every bit of state that I know about from NiFi
and then put my original flow.xml.gz in the conf directory of "node 1" and
deleted it from nodes 2-4, it came up with the processors correctly
started.  However, the flow.xml.gz file on "node 1" has almost 500
instances of the word "RUNNING" in it, while the flow.xml.gz file on nodes
2-4 have only 10 instances of the word "RUNNING".  Even when I make updates
on nodes 2-4 via UI and it updates the flow.xml.gz file on disk, it still
says "STOPPED" for almost everything on nodes 2-4 but "RUNNING" for almost
everything on node 1.


On Fri, May 12, 2017 at 4:18 PM, Tim Reardon <[hidden email]> wrote:

> I too have encountered all processors being stopped after restarting 1.2.0.
> (I am running a single node.) This happened several times, but on at least
> one occasion they remained running. I am pretty sure that in my case when
> the UI showed them stopped they really were stopped, and not running
> surreptitiously.
>
> On Fri, May 12, 2017 at 12:10 PM, Joe Gresock <[hidden email]> wrote:
>
> > One more key observation.. it actually appears that the processors are
> > running, even though their icons show that they are stopped.  For
> example,
> > the tasks/time keeps going up even though a GetSQS processor looks
> > stopped.  However, the fact that they appear stopped also seems to be
> > confusing the UI, which prevents me from starting any processors that
> > happen to have a thread running.
> >
> > On Fri, May 12, 2017 at 4:08 PM, Joe Gresock <[hidden email]> wrote:
> >
> > > I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all
> > > processors are stopped on startup.  However, the flow.xml.gz on disk
> > > appears to have the correct scheduledState values.  I'm afraid to touch
> > the
> > > flow in the UI, lest it save all 500 of my processors as stopped.
> > >
> > > Is there anything new in 1.2.0 that would cause this?
> > >
> > > --
> > > I know what it is to be in need, and I know what it is to have
> plenty.  I
> > > have learned the secret of being content in any and every situation,
> > > whether well fed or hungry, whether living in plenty or in want.  I can
> > > do all this through him who gives me strength.    *-Philippians
> 4:12-13*
> > >
> >
> >
> >
> > --
> > I know what it is to be in need, and I know what it is to have plenty.  I
> > have learned the secret of being content in any and every situation,
> > whether well fed or hungry, whether living in plenty or in want.  I can
> do
> > all this through him who gives me strength.    *-Philippians 4:12-13*
> >
>



--
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.    *-Philippians 4:12-13*