[
https://issues.apache.org/jira/browse/NIFI-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456594#comment-17456594
]
Joe Witt commented on NIFI-9465:
--------------------------------
The intent of this makes good sense. I'm not sure of an implementation option
that would work well. This also only protects users from CPU centric issues
generally speaking. Other types of resources (notably heap/memory) can still
be exhausted.
Definitely a concept worth more exploration just dont have a clear solution or
set of solutions in mind.
> Limit Max Thread Count in process groups
> ----------------------------------------
>
> Key: NIFI-9465
> URL: https://issues.apache.org/jira/browse/NIFI-9465
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.15.0
> Reporter: Wiktor Kubicki
> Priority: Minor
>
> Now we are able to set Maximum Timer Driven/Event Thread Count for whole
> instance of NiFi. It would be great if there will be possiblity to set it per
> process group.
> How it should looks?
> Thread scheduler should check running_threads_in_instance <
> instance_thread_limit *and* running_threads_in_group < group_thread_limit.
> Now there is only first part.
> Why?
> In multi-tenant enviroment we can limit permission but no resources like
> memory or CPU. This feature would give us a little better controll in that
> area and looks not very complicated to develop.
> On the other hand even in single tenant, there is advantage to limit it per
> process group - we can prevent whole instance against resources saturation if
> one group works harder.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
