[
https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104581#comment-14104581
]
Todd Palino commented on KAFKA-1605:
------------------------------------
There are a lot of concerns with this...
1) We are moving consumers away from talking to Zookeeper (with the new
consumer implementation that puts it all in the broker). Given that, we should
probably not move another component (producer) towards Zookeeper
2) Building on #1, if we want to restrict access to Zookeeper (to protect the
Kafka metadata), we cannot have clients, whether consumers or producers,
relying on it.
3) This requires adding a Zookeeper client to the producer. I don't see a
benefit in doing this, especially considering #1 above. You can put a DNS round
robin or a VIP in the metadata broker list.
4) Building on #3, if at some point in the future there is a desire to use an
alternate metadata store, it will be much simpler to do if only one component
needs to be changed.
All told, I just don't see any benefit in this proposal.
> 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)
