[
https://issues.apache.org/jira/browse/NIFI-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998676#comment-15998676
]
ASF subversion and git services commented on NIFI-2268:
-------------------------------------------------------
Commit 12249e5a08e40c550786edc83abd9d11454002fb in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=12249e5 ]
NIFI-2268: Instead of allowing HandleHttpRequest to run constantly calling
BlockingQueue.poll() as fast as possible, call BlockingQueue.poll(2,
TimeUnit.MILLISECONDS) to avoid overutilization of CPU when there is no work to
be done
This closes #1762.
Signed-off-by: Bryan Bende <[email protected]>
> HandleHttpRequest can use too many tasks and CPU
> ------------------------------------------------
>
> Key: NIFI-2268
> URL: https://issues.apache.org/jira/browse/NIFI-2268
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.7.0
> Reporter: Michael Moser
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.2.0
>
> Attachments: flow.xml.gz
>
>
> With the default settings of HandleHttpRequest, user reports 100% CPU usage
> and millions of scheduled tasks. When this processor doesn't have work to
> do, its onTrigger() should call ProcessContext.yield(). This is how the
> ListenHTTP processor works, so it's an established pattern.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
