You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Turcsanyi (Jira)" <ji...@apache.org> on 2021/03/24 14:03:00 UTC

[jira] [Resolved] (NIFI-8357) ConsumeKafka(Record)_2_0, ConsumeKafka(Record)_2_6 do not reconnect if using statically assigned partitions

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

Peter Turcsanyi resolved NIFI-8357.
-----------------------------------
    Resolution: Fixed

> ConsumeKafka(Record)_2_0, ConsumeKafka(Record)_2_6 do not reconnect if using statically assigned partitions
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-8357
>                 URL: https://issues.apache.org/jira/browse/NIFI-8357
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Critical
>             Fix For: 1.14.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If using statically assigned partitions in ConsumeKafka_2_0, ConsumeKafkaRecord_2_0, ConsumeKafka_2_6, or ConsumeKafkaRecord_2_6 (via adding {{partitions.}}{{<hostname}}> properties), when a client connection fails, it recreates connections but does not properly assign the partitions. As a result, the consumer stops consuming data from its partition(s), and the Kafka client that gets created gets leaked. This can slowly build up to leaking many of these connections and potentially could exhaust heap or cause IOException: too many open files.



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