You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dennis Jaheruddin (Jira)" <ji...@apache.org> on 2020/06/20 16:46:00 UTC
[jira] [Comment Edited] (NIFI-105) StandardRemoteGroupPort should
support event driven, but perhaps not allow an unbounded thread count
[ https://issues.apache.org/jira/browse/NIFI-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141129#comment-17141129 ]
Dennis Jaheruddin edited comment on NIFI-105 at 6/20/20, 4:45 PM:
------------------------------------------------------------------
I tried to reproduce this, but on my mac with a recent version of Nifi I did NOT manage to get to high CPU usage without data.
Perhaps I tested it wrong, but if someone could validate whether this is still an issue this may be closed. (Otherwise instructions to reproduce may be usefull).
was (Author: dennisjaheruddin):
I tried to reproduce this, but on my mac with a recent version of Nifi I did manage to get to high CPU usage without data.
Perhaps I tested it wrong, but if someone could validate whether this is still an issue this may be closed. (Otherwise instructions to reproduce may be usefull).
> StandardRemoteGroupPort should support event driven, but perhaps not allow an unbounded thread count
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-105
> URL: https://issues.apache.org/jira/browse/NIFI-105
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Priority: Minor
>
> Currently, this Port is very CPU-intensive if there's no data to send because it's continually checking for data.
> It's important that we consider both SEND and RECEIVE ports...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)