You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2016/11/03 15:32:59 UTC
[jira] [Updated] (NIFI-2850) Provide ability for a FlowFile to be
migrated from one Process Session to another
[ https://issues.apache.org/jira/browse/NIFI-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Zhurakousky updated NIFI-2850:
-----------------------------------
Assignee: Mark Payne (was: Oleg Zhurakousky)
> Provide ability for a FlowFile to be migrated from one Process Session to another
> ---------------------------------------------------------------------------------
>
> Key: NIFI-2850
> URL: https://issues.apache.org/jira/browse/NIFI-2850
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.1.0
>
>
> Currently, the MergeContent processor creates a separate ProcessSession for each FlowFile that it pulls. This is done so that we can ensure that we can commit all Process Sessions when a bin is full. Unfortunately, this means that MergeContent is required to call ProcessSession.get() many times, which adds a lot of contention on the FlowFile Queue. If we allow FlowFiles to be migrated from 1 session to another, we can have a session per bin, and then use ProcessSession.get(100) to greatly reduce lock contention. This will likely have benefits in other processors as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)