[
https://issues.apache.org/jira/browse/NIFI-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949170#comment-15949170
]
ASF subversion and git services commented on NIFI-3649:
-------------------------------------------------------
Commit 3aa1db6ee5d952aa67601e460331940f5e20a166 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3aa1db6 ]
NIFI-3636: Lazily copy FlowFile Attributes Hash Map instead of doing so eagerly.
Signed-off-by: Matt Burgess <[email protected]>
NIFI-3257: Added additional logging regarding timing information when
replicating requests across cluster in order to glean insight as to what is
taking so long when replicating some requests
Signed-off-by: Matt Burgess <[email protected]>
NIFI-3649: Buffer node responses when replicating HTTP Requests up to a maximum
buffer size
Signed-off-by: Matt Burgess <[email protected]>
NIFI-3636: Added unit test to ensure that flowfile attribute maps are copied
when appropriate
Signed-off-by: Matt Burgess <[email protected]>
NIFI-3636: Removed patch file that should not have been in commit
Signed-off-by: Matt Burgess <[email protected]>
This closes #1612
> 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
> Fix For: 1.2.0
>
>
> 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)