You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jul Tomten (Jira)" <ji...@apache.org> on 2021/07/09 08:23:00 UTC
[jira] [Updated] (NIFI-8765) WAIT processor uses > 100 % CPU when
files are on queue
[ https://issues.apache.org/jira/browse/NIFI-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jul Tomten updated NIFI-8765:
-----------------------------
Description:
2021-07-09 - Ignore the ticket at the moment. Issue can't be reprouduced after restart of NiFi.
I'm on NiFi 1.13.2
I have a WAIT processor and 2000 files queud up in the upstream connection
The problem is that the WAIT processor uses more than 100% CPU all the time as long as the messages are on queue.
Any idea about the problem?
Release Signal Identifier = ${uuid}
Target Signal Count = 1
Signal Counter Name = No value set
Wait Buffer Count = 1500
Releasable FlowFile Count = 1
Expiration Duration = 10 min
Attribute Copy Mode = Keep original
Wait Mode = Keep in the upstream connection
Wait Penalty Duration = 5 min
Number of Threads 10
I'd planned to have more than 10 000 000 messages on queue and then let them expire after 4 days. Some or all messages may be notified to proceed. Is the WAIT intended to handel such a scenario? More extensive documentation would be good.
Are you supposed to have multiple threads on the WAIT/NOTIFY processors? Seems like the MapCache hits problems ConcurrentModificationException. More extensive documentation would be good.
was:
I'm on NiFi 1.13.2
I have a WAIT processor and 2000 files queud up in the upstream connection
The problem is that the WAIT processor uses more than 100% CPU all the time as long as the messages are on queue.
Any idea about the problem?
Release Signal Identifier = ${uuid}
Target Signal Count = 1
Signal Counter Name = No value set
Wait Buffer Count = 1500
Releasable FlowFile Count = 1
Expiration Duration = 10 min
Attribute Copy Mode = Keep original
Wait Mode = Keep in the upstream connection
Wait Penalty Duration = 5 min
Number of Threads 10
I'd planned to have more than 10 000 000 messages on queue and then let them expire after 4 days. Some or all messages may be notified to proceed. Is the WAIT intended to handel such a scenario? More extensive documentation would be good.
Are you supposed to have multiple threads on the WAIT/NOTIFY processors? Seems like the MapCache hits problems ConcurrentModificationException. More extensive documentation would be good.
> WAIT processor uses > 100 % CPU when files are on queue
> -------------------------------------------------------
>
> Key: NIFI-8765
> URL: https://issues.apache.org/jira/browse/NIFI-8765
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.13.2
> Environment: ubuntu 2004 lts
> sap machine java 1.11
> Reporter: Jul Tomten
> Priority: Major
> Labels: WAIT, processor
>
> 2021-07-09 - Ignore the ticket at the moment. Issue can't be reprouduced after restart of NiFi.
>
> I'm on NiFi 1.13.2
> I have a WAIT processor and 2000 files queud up in the upstream connection
> The problem is that the WAIT processor uses more than 100% CPU all the time as long as the messages are on queue.
> Any idea about the problem?
>
> Release Signal Identifier = ${uuid}
> Target Signal Count = 1
> Signal Counter Name = No value set
> Wait Buffer Count = 1500
> Releasable FlowFile Count = 1
> Expiration Duration = 10 min
> Attribute Copy Mode = Keep original
> Wait Mode = Keep in the upstream connection
> Wait Penalty Duration = 5 min
>
> Number of Threads 10
>
>
> I'd planned to have more than 10 000 000 messages on queue and then let them expire after 4 days. Some or all messages may be notified to proceed. Is the WAIT intended to handel such a scenario? More extensive documentation would be good.
> Are you supposed to have multiple threads on the WAIT/NOTIFY processors? Seems like the MapCache hits problems ConcurrentModificationException. More extensive documentation would be good.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)