Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Thu, 28 Sep 2017 10:44:00 +0000 (UTC)
From: "Ismael Juma (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.12935404.1454203243000.224537.1506595440262@Atlassian.JIRA>
In-Reply-To: <JIRA.12935404.1454203243000@Atlassian.JIRA>
References: <JIRA.12935404.1454203243000@Atlassian.JIRA> <JIRA.12935404.1454203243993@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KAFKA-3177) Kafka consumer can hang when
 position() is called on a non-existing partition.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 28 Sep 2017 10:44:09 -0000


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

Ismael Juma updated KAFKA-3177:
-------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0

> Kafka consumer can hang when position() is called on a non-existing partition.
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-3177
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3177
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.9.0.0
>            Reporter: Jiangjie Qin
>            Assignee: Jason Gustafson
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> This can be easily reproduced as following:
> {code}
> {
>     ...
>     consumer.assign(SomeNonExsitingTopicParition);
>     consumer.position();
>     ...
> }
> {code}
> It seems when position is called we will try to do the following:
> 1. Fetch committed offsets.
> 2. If there is no committed offsets, try to reset offset using reset strategy. in sendListOffsetRequest(), if the consumer does not know the TopicPartition, it will refresh its metadata and retry. In this case, because the partition does not exist, we fall in to the infinite loop of refreshing topic metadata.
> Another orthogonal issue is that if the topic in the above code piece does not exist, position() call will actually create the topic due to the fact that currently topic metadata request could automatically create the topic. This is a known separate issue.


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