[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429672#comment-13429672
]
Yang Ye commented on KAFKA-369:
-------------------------------
I am thinking about the exception handling in updateInfo() function. The topic
level error code maybe NoError while there may still be partition-level error
code. In this case, it's not appropriate for us to put the (topic,
topicMetadata) into the cache. Of course we can put in the "tailed"
topicMetatData, which only contains partitionMetadata whose error code is
NoError, but this is kind of hacky.
Also it's not bad to just throw exception to the client, because this function
is called on demand --- when the client wants to send messages to a topic. If
some topic is erroneous, the send need to be failed.
> remove ZK dependency on producer
> --------------------------------
>
> Key: KAFKA-369
> URL: https://issues.apache.org/jira/browse/KAFKA-369
> Project: Kafka
> Issue Type: Sub-task
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Yang Ye
> Attachments: kafka_369_v1.diff, kafka_369_v2.diff, kafka_369_v3.diff,
> kafka_369_v4.diff
>
> Original Estimate: 252h
> Remaining Estimate: 252h
>
> Currently, the only place that ZK is actually used is in BrokerPartitionInfo.
> We use ZK to get a list of brokers for making TopicMetadataRequest requests.
> Instead, we can provide a list of brokers in the producer config directly.
> That way, the producer client is no longer dependant on ZK.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
