You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Tamas Palfy (Jira)" <ji...@apache.org> on 2020/02/04 12:47:00 UTC

[jira] [Assigned] (NIFI-7081) Improve handling of Load Balanced Connections when one node is slow

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

Tamas Palfy reassigned NIFI-7081:
---------------------------------

    Assignee: Tamas Palfy

> Improve handling of Load Balanced Connections when one node is slow
> -------------------------------------------------------------------
>
>                 Key: NIFI-7081
>                 URL: https://issues.apache.org/jira/browse/NIFI-7081
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Tamas Palfy
>            Priority: Major
>
> When a connection is configured to use Round Robin load balancing, the FlowFIle Queue works by queuing up one FlowFile to be processed locally, one to be sent to Node 2, one to be sent to Node 3, the next one to be locally processed, etc. (in this case, assuming a 3-node cluster).
> If one node in a cluster is slow, though, we can have a situation where the local partition is empty and the partition for Node 2 is empty. But Node 3's partition is full, because Node 3 is not processing the data quickly enough. As a result, on Node 1, the queue ends up applying backpressure, with all FlowFiles in the queue waiting to be pushed to Node 3.
> In such a situation, we end up preventing any data from being processed by Node 1 or Node 2. It would be advantageous to improve this so that Node 1 and Node 2 could still be busy processing data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)