[
https://issues.apache.org/jira/browse/KAFKA-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-820:
--------------------------------
Attachment: kafka-820-v1.patch
Two changes -
1. Modified topic metadata request handling to return the broker metadata for
the rest of the brokers, even if one of them is offline. Also, modified it to
throw an exception if even one of the brokers is offline so that error code
will get returned to the client
2. ReplicaNotAvailableException is irrelevant to the producer. It should not
log the stack trace for it inside BrokerPartitionInfo.updateInfo(). This should
only happen for UnknownTopicOrPartitionException and LeaderNotAvailableException
> 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
