You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2017/03/28 15:16:42 UTC
[jira] [Updated] (NIFI-3649) Parallelize Consumption of Cluster
Replication Responses
[ https://issues.apache.org/jira/browse/NIFI-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-3649:
-----------------------------
Description: Currently, when we replicate a REST API call to all nodes in the cluster, we wait until we get back a Response object for each node. We then go to the Response Mapper and merge those responses into 1 NodeResponse. This merging is done serially, and this is where we actually do the reading of the response. We need to instead do this merging in parallel or buffer responses in parallel and then merge then when done. (was: Currently, when we replicate a REST API call to all nodes in the cluster, we wait until we get back a Response object for each node. We then go to the Response Mapper and merge those responses into 1 NodeResponse. This merging is done serially, and this is where we actually do the reading of the response. We need to instead do this merging in parallel.)
> Parallelize Consumption of Cluster Replication Responses
> --------------------------------------------------------
>
> Key: NIFI-3649
> URL: https://issues.apache.org/jira/browse/NIFI-3649
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
>
> Currently, when we replicate a REST API call to all nodes in the cluster, we wait until we get back a Response object for each node. We then go to the Response Mapper and merge those responses into 1 NodeResponse. This merging is done serially, and this is where we actually do the reading of the response. We need to instead do this merging in parallel or buffer responses in parallel and then merge then when done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)