[jira] [Commented] (KAFKA-369) remove ZK dependency on producer

["Otis Gospodnetic (JIRA)" <ji...@apache.org>]

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

Otis Gospodnetic commented on KAFKA-369:
----------------------------------------

I'm completely late on this and don't have the full context, so my apologies if this is a naive question, but why would you want to have addresses of brokers in producer's configs and not have producer get that from Zookeeper?  I thought using ZK for cluster-wide config sharing was a good thing, but there must be some reason why you chose not to do that here.  Can anyone shed some light on this.... 14 months after the commit? :)


> 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)