You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/01/31 10:50:00 UTC

[jira] [Resolved] (FLINK-10774) connection leak when partition discovery is disabled and open throws exception

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

Till Rohrmann resolved FLINK-10774.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0
                   1.7.2
                   1.6.4

Fixed via
1.8.0:
a9e18fa921
232560d0c9
83183ce4d9
3cbaabc527

1.7.2:
af83b991f5
4789b3f768
198c4001fc
8012ab17bc

1.6.4:
402f23507b
2a5d97d49e
c2150648de
1b9c464ab3

> connection leak when partition discovery is disabled and open throws exception
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-10774
>                 URL: https://issues.apache.org/jira/browse/FLINK-10774
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>    Affects Versions: 1.4.2, 1.5.5, 1.6.2
>            Reporter: Steven Zhen Wu
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.4, 1.7.2, 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Here is the scenario to reproduce the issue
>  * partition discovery is disabled
>  * open method throws an exception (e.g. when broker SSL authorization denies request)
> In this scenario, run method won't be executed. As a result, _partitionDiscoverer.close()_ won't be called. that caused the connection leak, because KafkaConsumer is initialized but not closed. That has caused outage that brought down our Kafka cluster, when a high-parallelism job got into a restart/failure loop.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)