Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 2 Jan 2018 18:24:00 +0000 (UTC)
From: "Guozhang Wang (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.13125752.1513641862000.557526.1514917440733@Atlassian.JIRA>
In-Reply-To: <JIRA.13125752.1513641862000@Atlassian.JIRA>
References: <JIRA.13125752.1513641862000@Atlassian.JIRA> <JIRA.13125752.1513641862296@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (KAFKA-6383) StreamThread.shutdown doesn't clean
 up completely when called before StreamThread.start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 Jan 2018 18:24:05 -0000


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

Guozhang Wang resolved KAFKA-6383.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

> StreamThread.shutdown doesn't clean up completely when called before StreamThread.start
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-6383
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6383
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 1.0.0
>            Reporter: Rohan Desai
>            Assignee: Rohan Desai
>             Fix For: 1.1.0
>
>
> The following code leaks a producer network thread:
> {code}
> ks = new KafkaStreams(...);
> ks.close();
> {code}
> The underlying issue is that KafkaStreams creates a bunch of StreamsThreads via StreamThread.create, which in turn creates a bunch of stuff (including a producer). These resources are cleaned up only when the thread exits. So if the thread was never started, then they are never cleaned up. StreamThread.shutdown should clean up if it sees that the thread has never been started.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)