You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Sriharsha Chintalapani (JIRA)" <ji...@apache.org> on 2015/02/17 19:50:11 UTC

[jira] [Commented] (KAFKA-1867) liveBroker list not updated on a cluster with no topics

    [ https://issues.apache.org/jira/browse/KAFKA-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324659#comment-14324659 ] 

Sriharsha Chintalapani commented on KAFKA-1867:
-----------------------------------------------

[~nehanarkhede] pinging for a review. Thanks.

> liveBroker list not updated on a cluster with no topics
> -------------------------------------------------------
>
>                 Key: KAFKA-1867
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1867
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jun Rao
>            Assignee: Sriharsha Chintalapani
>             Fix For: 0.8.3
>
>         Attachments: KAFKA-1867.patch, KAFKA-1867.patch, KAFKA-1867_2015-01-25_21:07:47.patch
>
>
> Currently, when there is no topic in a cluster, the controller doesn't send any UpdateMetadataRequest to the broker when it starts up. As a result, the liveBroker list in metadataCache is empty. This means that we will return incorrect broker list in TopicMetatadataResponse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)