[
https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103492#comment-14103492
]
Joe Stein edited comment on KAFKA-1605 at 8/20/14 6:36 AM:
-----------------------------------------------------------
fwiw, sometimes what people do is a DNS like mybrokerlist.mycompany.com and put
that in the producer properties ... this way if the initial broker it connects
to is no longer there DNS can change IP to broker that is for the inital meta
data request on startup connection (or put 2 IP in there round robin DNS).
was (Author: joestein):
fwiw, sometimes what people do is a DNS like mybrokerlist.mycompany.com and put
that in.... this way if the initial broker it connects to is no longer there
DNS can change IP to broker that is for the inital meta data request on startup
connection (or put 2 IP in there round robin DNS).
> 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)
