Downtime behaviour

[Nifi Rocks <ni...@gmail.com>]

Hi community.
Suppose I set the start of my flow to 8 o'clock. Now I shut down the
container between 7:59 and 8:01 and restart it afterwards. Will my flow
start at 8:02?

If the flow is not triggered afterwards, several things will get
complicated. I would have to inform all users during upgrades and first
find out which processes would run during the maintenance period.

Re: Downtime behaviour

[Jo...@swisscom.com]

If you mean “Cron driven” scheduling strategy which has exactly a start of 08:00:00, then it won’t run afterwards. If you use “Timer driven” scheduling, it will start again after a restart. So all depends on your scheduling strategy.


From: Mike Thomsen <mi...@gmail.com>
Reply to: "users@nifi.apache.org" <us...@nifi.apache.org>
Date: Wednesday, 4 March 2020 at 12:25
To: "users@nifi.apache.org" <us...@nifi.apache.org>
Subject: Re: Downtime behaviour

I've never set a flow to run at an exact time of the day, but giving yourself such a tight window to have everything come back doesn't seem like a good practice for system maintenance.

On Wed, Mar 4, 2020 at 12:24 AM Nifi Rocks <ni...@gmail.com>> wrote:
Hi community.
Suppose I set the start of my flow to 8 o'clock. Now I shut down the container between 7:59 and 8:01 and restart it afterwards. Will my flow start at 8:02?

If the flow is not triggered afterwards, several things will get complicated. I would have to inform all users during upgrades and first find out which processes would run during the maintenance period.

Re: Downtime behaviour

[Mike Thomsen <mi...@gmail.com>]

I've never set a flow to run at an exact time of the day, but giving
yourself such a tight window to have everything come back doesn't seem like
a good practice for system maintenance.

On Wed, Mar 4, 2020 at 12:24 AM Nifi Rocks <ni...@gmail.com> wrote:

> Hi community.
> Suppose I set the start of my flow to 8 o'clock. Now I shut down the
> container between 7:59 and 8:01 and restart it afterwards. Will my flow
> start at 8:02?
>
> If the flow is not triggered afterwards, several things will get
> complicated. I would have to inform all users during upgrades and first
> find out which processes would run during the maintenance period.
>