[
https://issues.apache.org/jira/browse/NIFI-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813478#comment-16813478
]
ASF subversion and git services commented on NIFI-5464:
-------------------------------------------------------
Commit 38db4e97cd619b3a3c46e2e6a2e71e25df98ad0b in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=38db4e9 ]
NIFI-5464: Consider ports invalid unless they have both incoming and outgoing
connections
This closes #3417.
Signed-off-by: Bryan Bende <[email protected]>
> Local Ports are able to be started without incoming connections, then use a
> lot of CPU
> --------------------------------------------------------------------------------------
>
> Key: NIFI-5464
> URL: https://issues.apache.org/jira/browse/NIFI-5464
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, validation of a LocalPort simply checks that it has an outgoing
> connection. This means that it's possible to create an outgoing connection
> for a port but not have any incoming connections. When this happens, if the
> Port is started, the framework determines that it is a "source component"
> because it has no incoming connections. As such, it is never yielded via the
> "bored yield duration". This results in high CPU usage.
> The fix in this case, I believe, is to address the validation. We should not
> allow a Local Port to be enabled if it has no incoming connections.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
