Hi Mark,
Thanks for the response.
My flow.xml.gz file size is 14 Mb.
Regards,
Sanjeet
On Thu, 13 Aug 2020, 10:27 pm Mark Payne, wrote:
> Actually, I take back what I said. I was a little too quick to jump to
> conclusions about what the issue was. There was an issue addressed that
> should imp
Actually, I take back what I said. I was a little too quick to jump to
conclusions about what the issue was. There was an issue addressed that should
improve startup time. But what you’re seeing here is unrelated, as you’re
enchanting OutOfMemoryError. The long time is likely related to garbage
Sanjeet,
I believe this should be addressed in 1.12.0, which should be released very
soon.
Thanks
-Mark
On Aug 13, 2020, at 4:13 AM, sanjeet rath
mailto:rath.sanj...@gmail.com>> wrote:
Hi Team,
I have migrated my flows.xml.gz, users.xml, authorization.xml from 1.8 env to
1.11.4 environment
...true and I believe that has also been improved. But could be wrong on
that.
On Thu, Aug 13, 2020 at 9:26 AM Brandon DeVries
wrote:
> Mohit,
>
> How many flowfiles are currently on the instance? Sometimes a very large
> number of flowfiles can result in slower start times.
>
> Brandon
>
> --
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
Sent: Thursday, August 13, 2020 12:10:51 PM
To: users@nifi.apache.org
Subject: Re: Nifi takes to
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 Wit
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
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 st
Hi Joe,
Many thanks for pointing this out.
Right now, I am implementing the case when files are already there when
reading. Next step will be to implement both sending and receiving processes.
I implemented the retry loop and it works perfectly.
Thanks for all suggestions and comments!
Valent
Dear All,
I am encountering issue with LDAP integration.
1. I have completed LDAP configuration (ldap-provider) according to
documentation.
2. I added IU certificate and configured other pieces of the MS AD LDAP
integration (authorizers.xml, login-identity-providers.xml and
nifi.properties).
3.
Mike, Bryan - thanks for the info and the offer of help exploring self
describing messages - I’ll leave the JIRA ticket for the time being to avoid
wasting your time, but if we proceed with development I’ll get back in touch /
contribute wherever possible.
Thanks,
Chris
> On 12 Aug 2020, at 2
Hi Team,
I have migrated my flows.xml.gz, users.xml, authorization.xml from 1.8 env
to 1.11.4 environment .(12k processor are therr in flow)
There are no error in the log file, the issue is taking 10 mintues to
server up and with all node connected.
The warning logs , which i am suspecting is cau
12 matches
Mail list logo
