[
https://issues.apache.org/jira/browse/KAFKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789851#comment-13789851
]
Neha Narkhede commented on KAFKA-369:
-------------------------------------
In addition to the above, the cluster metadata approach is more scalable since
you get all metadata for several topics in one RPC roundtrip vs reading several
paths per topic from zookeeper.
> 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
> Fix For: 0.8
>
> Attachments: kafka_369_v1.diff, kafka_369_v2.diff, kafka_369_v3.diff,
> kafka_369_v4.diff, kafka_369_v5.diff, kafka_369_v6.diff, kafka_369_v7.diff,
> kafka_369_v8.diff, kafka_369_v9.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 was sent by Atlassian JIRA
(v6.1#6144)
