[
https://issues.apache.org/jira/browse/KAFKA-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607868#comment-13607868
]
Neha Narkhede commented on KAFKA-820:
-------------------------------------
The return value is not irrelevant. As I explained, even if one broker is down,
it aborts sending the broker data for the rest of the brokers. The impression
it gives the client is that all the brokers are dead. The reason it throws the
exception at the end is because we need to send the appropriate error code to
the client if at least one broker is down.
> 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
