Mohit,

How many flowfiles are currently on the instance?  Sometimes a very large 
number of flowfiles can result in slower start times.

Brandon

________________________________
From: Pierre Villard <pierre.villard...@gmail.com>
Sent: Thursday, August 13, 2020 12:10:51 PM
To: users@nifi.apache.org <users@nifi.apache.org>
Subject: Re: Nifi takes too long to start(~ 30 minutes)

Hi,

I'm surprised this is something you observe in the election process part.
I've constantly seen quick startup times even with thousands of components in 
the flow.
I'd look into the logs and maybe turn on some debug logs to find out what's 
going on.

Pierre

Le jeu. 13 août 2020 à 16:33, Joe Witt 
<joe.w...@gmail.com<mailto:joe.w...@gmail.com>> a écrit :
Mohit,

You almost certainly want to take that same flow and setup a cluster on a more 
recent version of NiFi to compare startup times.  For flows with thousands of 
components there are important improvements which have occurred in the past 
year and a half.

Startup time, user perceived behavior in the UI on continuous operations, etc.. 
have been improved. Further you can now hot load new versions of nars which 
should reduce the need to restart.

We also will have 1.12 out hopefully within days so that could be interesting 
for you as well.

Thanks

On Thu, Aug 13, 2020 at 7:18 AM Mohit Jain 
<mo...@open-insights.com<mailto:mo...@open-insights.com>> wrote:
Hi Team,

I am using a single node NiFi 1.9.0 cluster. It takes more than 30 minutes to 
start each time it is restarted. There are more than 100 flows on the NiFi UI 
with an average of 25 processors per flow. It takes around 25-30 minutes to 
reach the cluster election process after which it gets started in a minute.

Is this an expected behaviour that startup time is directly proportional to the 
number of processors in the Canvas? Or is there a way to reduce the NiFi 
startup time?

Any leads would be appreciated.

Thanks,
Mohit

Reply via email to