;
Reply-To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
mailto:users@nifi.apache.org>>
Date: Sunday, October 13, 2019 at 6:12 PM
To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
mailto:users@nifi.apache.org>>
Subject: Re: High CPU consumption
Bende"
To: "users"
Sent: Wednesday, October 16, 2019 4:32:06 PM
Subject: Re: High CPU consumption
Hi Luis,
Can you describe the part of the flow that turned out to be a problem
a little more?
Was it a port on the root canvas used for s2s that was then connected
into a process gr
rything is
>> correctly back to where it should be
>>
>> Then use the list of processors and fixes to make changes.
>>
>> ---
>>
>> Evan Reynolds
>> e...@usermind.com
>>
>>
>
ing around stopping things, this just makes sure everything is
> correctly back to where it should be
>
> Then use the list of processors and fixes to make changes.
>
> ---
>
> Evan Reynolds
> e...@usermind.com
>
>
> *From: *Jon Logan
> *Reply-To: *"use
it is worthy.
Thank you all for the tips and recommendations.
LC
From: "Evan Reynolds"
To: "users"
Sent: Tuesday, October 15, 2019 5:40:07 PM
Subject: Re: High CPU consumption
I have found two issues that can cause high CPU when idle (high being about
200%
xes to make changes.
>
> ---
>
> Evan Reynolds
> e...@usermind.com <mailto:e...@usermind.com>
>
>
> From: Jon Logan
> Reply-To: "users@nifi.apache.org"
> Date: Sunday, October 13, 2019 at 6
.org"
Date: Sunday, October 13, 2019 at 6:12 PM
To: "users@nifi.apache.org"
Subject: Re: High CPU consumption
That isn't logback, that lists all jars on your classpath, the first of which
happens to be logback.
If you send a SIGKILL3 (you can send it in HTOP) it will du
lated to logback jar is the one that
> is eating up all the CPU ?
> Please take a look at the attached image.
>
> Thanks,
>
> LC
>
> --
> *From: *"Aldrin Piri"
> *To: *"users"
> *Sent: *Sunday, October 13, 2019 9:
---
> *From: *"Aldrin Piri"
> *To: *"users"
> *Sent: *Sunday, October 13, 2019 9:30:47 PM
> *Subject: *Re: High CPU consumption
>
> Luis, please feel free to give us some information on your flow so we can
> help you track down problemat
Luis, please feel free to give us some information on your flow so we can
help you track down problematic areas as well.
On Sun, Oct 13, 2019 at 3:56 PM Jon Logan wrote:
> You should put a profiler on it to be sure.
>
> Just because your processors aren't processing data doesn't mean they are
>
You should put a profiler on it to be sure.
Just because your processors aren't processing data doesn't mean they are
idle though -- many have to poll for new data, especially sources -- ex.
connecting to Kafka, etc, will itself consume some CPU.
But again, you should attach a profiler before par
HI,
I've struggling to reduce my nifi installation CPU consumption. Even in idle
state, all processors running but no data flowing, it is beyond 60% CPU
consumption, with peaks of 200%.
What I've done so far
- Read and followed every instruction/post about tuning NIFI I've found
googling.
12 matches
Mail list logo