[
https://issues.apache.org/jira/browse/KAFKA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103498#comment-14103498
]
Prashant Deva commented on KAFKA-1605:
--------------------------------------
the point is, a broker ip (yes i know only 1 is needed) needs to be given to
the producer.
if we decide to move the brokers to a different set of servers, then not even 1
will match and we have to update the code and redeploy our whole app.
Imagine a blue-green deployment where a new server is always constructed on an
update. In this case, the entire set of broker ips will always be refreshed
upon updating the broker boxes. This means we have to go in and change the ip
for brokers in the code manually each time we deploy a new producer. it breaks
the whole continuous deployment process.
I dont understand what you mean by 'better' in this case.
> 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)
