Nifi service stopped with no 'stop' request?

[Cheryl Jennings <ch...@gmail.com>]

Hi Everyone,

I had nifi running overnight, communicating between two nodes.  When I
checked in the morning, the nifi service on one of the nodes had stopped.

Normally when issuing a 'service nifi stop', I see an entry in
nifi-bootstrap.log that says:
org.apache.nifi.bootstrap.Command Apache NiFi has accepted the Shutdown
Command and is shutting down now

But this time, I only see this message in nifi-app.log, and no indication
in nifi-bootstrap.log that
a Shutdown Command was issued:
org.apache.nifi.BootstrapListener Received SHUTDOWN request from Bootstrap

Is there any reason nifi would stop like this without an explicit `service
stop|restart`?

Thanks!
-Cheryl

Re: Nifi service stopped with no 'stop' request?

[Joe Witt <jo...@gmail.com>]

Cheryl - in addition to the ask from James can you take a look for
anything interesting in the nifi-app.log about ERROR/WARN.

Thanks

On Fri, Feb 3, 2017 at 12:31 PM, James Wing <jv...@gmail.com> wrote:
> Cheryl,
>
> I'm not aware of any good explanation for that, or open issues on this
> topic.  Can you share more detail on the OS, JVM, NiFi versions?
>
> Thanks,
>
> James
>
> On Thu, Feb 2, 2017 at 12:14 PM, Cheryl Jennings <ch...@gmail.com> wrote:
>>
>> Hi Everyone,
>>
>> I had nifi running overnight, communicating between two nodes.  When I
>> checked in the morning, the nifi service on one of the nodes had stopped.
>>
>> Normally when issuing a 'service nifi stop', I see an entry in
>> nifi-bootstrap.log that says:
>> org.apache.nifi.bootstrap.Command Apache NiFi has accepted the Shutdown
>> Command and is shutting down now
>>
>> But this time, I only see this message in nifi-app.log, and no indication
>> in nifi-bootstrap.log that
>> a Shutdown Command was issued:
>> org.apache.nifi.BootstrapListener Received SHUTDOWN request from Bootstrap
>>
>> Is there any reason nifi would stop like this without an explicit `service
>> stop|restart`?
>>
>> Thanks!
>> -Cheryl
>
>

Re: Nifi service stopped with no 'stop' request?

[James Wing <jv...@gmail.com>]

Cheryl,

I'm not aware of any good explanation for that, or open issues on this
topic.  Can you share more detail on the OS, JVM, NiFi versions?

Thanks,

James

On Thu, Feb 2, 2017 at 12:14 PM, Cheryl Jennings <ch...@gmail.com> wrote:

> Hi Everyone,
>
> I had nifi running overnight, communicating between two nodes.  When I
> checked in the morning, the nifi service on one of the nodes had stopped.
>
> Normally when issuing a 'service nifi stop', I see an entry in
> nifi-bootstrap.log that says:
> org.apache.nifi.bootstrap.Command Apache NiFi has accepted the Shutdown
> Command and is shutting down now
>
> But this time, I only see this message in nifi-app.log, and no indication
> in nifi-bootstrap.log that
> a Shutdown Command was issued:
> org.apache.nifi.BootstrapListener Received SHUTDOWN request from Bootstrap
>
> Is there any reason nifi would stop like this without an explicit `service
> stop|restart`?
>
> Thanks!
> -Cheryl
>

Re: Many systems - big flow graphs?

[Joe Witt <jo...@gmail.com>]

Uwe

Happy to have this be a longer dialogue just wanted to get a quick
response back.  You mentioned having unconnected flows separate from
each other.  Yes this is absolutely how it is done for really massive
large scale sets of disparate flows.  The process group concept allows
you to logically create abstractions/groups of flows.  People tend to
name their process groups and processor in meaningful ways.  We have
the search bar in the top-right for fast-find of such components even
if buried very deep in the flow.

This approach works quite well and helps enforce that you keep things
organized and allows you to 'refactor' the flows by moving around and
restructuring groups/etc..

Thanks
Joe

On Thu, Feb 2, 2017 at 5:39 PM, Uwe Geercken <uw...@web.de> wrote:
> Hello,
>
> excuse my question, but I still have not fully understood how one would
> logically handle large flow graphs. If I have many systems involved and many
> different types of output, would I really put everything in one flow? Or is
> this a misunderstanding on my side? If you put everything in one flow is it
> not getting messy and hard to search and debug? That would have an influence
> on quality at some point in time.
>
> Or would you logically seperate things that do not really belong together
> and run them in flows on different servers - unconnected and seperated from
> the others? Would that be the idea?
>
> I would be happy to hear some of your thoughts or findings from your
> experience.
>
> Rgds,
>
> Uwe
>
>