[
https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103490#comment-14103490
]
Joe Stein commented on KAFKA-1605:
----------------------------------
The metadata api handles service discovery of the brokers for the producers.
All you need is to be able to connect to 1 (or two in case the other 1 goes
down) brokers and then you pass in a list of topics (or null for all topics)
and get back the broker information for each topic's partitions, etc, etc,
etc... This is all done under the hood for you just point the producer to any
broker and away it goes.
This is *WAY* better than connecting to zookeeper especially for non JVM
clients. Specific details here if you are interested
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-MetadataAPI
> Producer should not require metadata.broker.list
> ------------------------------------------------
>
> Key: KAFKA-1605
> URL: https://issues.apache.org/jira/browse/KAFKA-1605
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8.1.1
> Reporter: Prashant Deva
>
> Producer should just query the zookeeper and get the list of brokers from it
> directly.
> With the current requirement the producer explicitly needs to know the ips of
> all the brokers. So if you decide to replace them, you have to change the
> Producer's code.
> Isnt the whole point of using a zookeeper to avoid these kind of dependencies?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
