You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2013/03/20 17:39:17 UTC

[jira] [Commented] (KAFKA-820) Topic metadata request handling fails to return all metadata about replicas

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

Jun Rao commented on KAFKA-820:
-------------------------------

Thanks for the patch. Not sure that I understand the changes in AdminUtils.getBrokerInfoFromCache(). It seems to me that with or w/o the patch, the method will throw an exception if at least one of the items in brokerIds can't be converted to a Broker object, in which case the return value is irrelevant.
                
> Topic metadata request handling fails to return all metadata about replicas
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-820
>                 URL: https://issues.apache.org/jira/browse/KAFKA-820
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>            Priority: Blocker
>              Labels: kafka-0.8
>         Attachments: kafka-820-v1.patch
>
>
> The admin utility that fetches topic metadata needs improvement in error handling. While fetching replica and isr broker information, if one of the replicas is offline, it fails to fetch the replica and isr info for the rest of them. This creates confusion on the client since it seems to the client the rest of the brokers are offline as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira