You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gábor Gyimesi (Jira)" <ji...@apache.org> on 2022/01/03 14:37:00 UTC
[jira] [Updated] (MINIFICPP-1706) Rework script engine management in ExecuteScript processor

     [ https://issues.apache.org/jira/browse/MINIFICPP-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gábor Gyimesi updated MINIFICPP-1706:
-------------------------------------
    Description: 
In [MINIFICPP-1222|https://issues.apache.org/jira/browse/MINIFICPP-1222] an issue was raised that the script engines were not handled correctly by allowing more engines in the queue than the maximum number of concurrent tasks defined in the ExecutePythonProcessor processor. This issue is also present in the ExecuteScript processor.

In the ExecutePythonProcessor processor the queue was eventually removed in https://github.com/apache/nifi-minifi-cpp/pull/1227 due the python's GIL not allowing real concurrency. In the ExecuteScript processor we should have a solution that allows concurrency with LUA engines limiting the number of engines to the maximum concurrent tasks limit, but having a single engine for Python script executions.

  was:
In [MINIFICPP-1222|https://issues.apache.org/jira/browse/MINIFICPP-1222] an issue was raised that the script engines were not handled correctly by allowing more engines in the queue than the maximum number of concurrent operations in the ExecutePythonProcessor processor. This issue is also present in the ExecuteScript processor.

In the ExecutePythonProcessor processor the queue was eventually removed in https://github.com/apache/nifi-minifi-cpp/pull/1227 due the python's GIL not allowing real concurrency. In the ExecuteScript processor we should have a solution that allows concurrency with LUA engines limiting the number of engines to the maximum concurrent operations limit, but having a single engine for Python script executions.


> Rework script engine management in ExecuteScript processor
> ----------------------------------------------------------
>
>                 Key: MINIFICPP-1706
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1706
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Gábor Gyimesi
>            Priority: Minor
>
> In [MINIFICPP-1222|https://issues.apache.org/jira/browse/MINIFICPP-1222] an issue was raised that the script engines were not handled correctly by allowing more engines in the queue than the maximum number of concurrent tasks defined in the ExecutePythonProcessor processor. This issue is also present in the ExecuteScript processor.
> In the ExecutePythonProcessor processor the queue was eventually removed in https://github.com/apache/nifi-minifi-cpp/pull/1227 due the python's GIL not allowing real concurrency. In the ExecuteScript processor we should have a solution that allows concurrency with LUA engines limiting the number of engines to the maximum concurrent tasks limit, but having a single engine for Python script executions.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)