nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-338) Threads can be unbounded per flow configuration
Date Tue, 12 Sep 2017 17:52:00 GMT

    [ https://issues.apache.org/jira/browse/MINIFI-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163354#comment-16163354
] 

ASF subversion and git services commented on MINIFI-338:
--------------------------------------------------------

Commit ead9e84ec163252b63e7889de925e6eac72e1b63 in nifi-minifi-cpp's branch refs/heads/master
from Marc Parisi
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=ead9e84 ]

MINIFI-338: Address linter errors


> Threads can be unbounded per flow configuration
> -----------------------------------------------
>
>                 Key: MINIFI-338
>                 URL: https://issues.apache.org/jira/browse/MINIFI-338
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++
>            Reporter: marco polo
>            Assignee: marco polo
>             Fix For: cpp-0.3.0
>
>
> The number of tasks configured by a given processor should be bounded by a thread pool
configuration. Currently the schedulers have no concept of a thread pool except for the component
life cycle thread pool. We should transition the tasks to a thread pool shared by the scheduler
and is globally configurable to better minimize the impact of processors. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message