You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/28 15:57:12 UTC
[jira] [Commented] (NIFI-1822) Allow concurrent execution of
ExecuteScript
[ https://issues.apache.org/jira/browse/NIFI-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262170#comment-15262170 ]
ASF GitHub Bot commented on NIFI-1822:
--------------------------------------
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/387
NIFI-1822: Allow concurrent execution in ExecuteScript
Added a ScriptEngine pool for use by ExecuteScript, to enable it to run with multiple concurrent tasks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi NIFI-1822
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/387.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #387
----
commit 0d3aac1cdb5d6d2ed2779ade8b3b48169ccf6f21
Author: Matt Burgess <ma...@apache.org>
Date: 2016-04-28T13:53:16Z
NIFI-1822: Allow concurrent execution in ExecuteScript
----
> Allow concurrent execution of ExecuteScript
> -------------------------------------------
>
> Key: NIFI-1822
> URL: https://issues.apache.org/jira/browse/NIFI-1822
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> Currently ExecuteScript is annotated as TriggerSerially, meaning only one task can be running at a time. This causes issues for throughput, and can become a severe bottleneck in a flow.
> Originally this was done because the bindings for the session, context, etc. were put on a single script engine, so multiple tasks would clobber each other's bindings. However as a tradeoff (memory for capability), it would be better to have a "pool" of Script Engine instances, whose size is perhaps the max number of concurrent tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)