You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Murtuza Shareef (Jira)" <ji...@apache.org> on 2020/03/25 03:26:00 UTC
[jira] [Updated] (MINIFICPP-1186) Separate C2Agent from
FlowController threadpool.
[ https://issues.apache.org/jira/browse/MINIFICPP-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murtuza Shareef updated MINIFICPP-1186:
---------------------------------------
Description:
Currently C2 operations operate in a common threadpool shared by the agent components. It makes it hard to cooperate between FlowController and C2Agent when we are handling configuration/flow updates from C2 that requires us to restart all components including the threadpool.
It could be much easier and cleaner if we keep C2Agent separated out from the shared threadpool and manage the FlowController operations without having to worry about stopping and starting C2Agent while updating flow configuration.
was:
Currently C2 operations operate in a common threadpool shared by the agent components. It makes it hard to cooperate between FlowController and C2Agent when we are handing configuration/flow updates from C2 that requires us to restart all components including the threadpool.
It could be much easier and cleaner if we keep C2Agent separated out from the shared threadpool and manage the FlowController operations without having to worry about stopping and starting C2Agent while updating flow configuration.
> Separate C2Agent from FlowController threadpool.
> ------------------------------------------------
>
> Key: MINIFICPP-1186
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1186
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Murtuza Shareef
> Assignee: Murtuza Shareef
> Priority: Major
>
> Currently C2 operations operate in a common threadpool shared by the agent components. It makes it hard to cooperate between FlowController and C2Agent when we are handling configuration/flow updates from C2 that requires us to restart all components including the threadpool.
> It could be much easier and cleaner if we keep C2Agent separated out from the shared threadpool and manage the FlowController operations without having to worry about stopping and starting C2Agent while updating flow configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)