[
https://issues.apache.org/jira/browse/KAFKA-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951532#comment-13951532
]
Jay Bae commented on KAFKA-1348:
--------------------------------
Let me explain again. Let's assume that initially, the broker cluster has 3
instances with the following hostname:
- ec2-12-123-456-111.compute-1.amazonaws.com
- ec2-12-123-456-222.compute-1.amazonaws.com
- ec2-12-123-456-333.compute-1.amazonaws.com
When the ec2-12-123-456-111.compute-1.amazonaws.com is terminated by AWS and it
launches new one, the cluster will contain
- ec2-12-123-456-444.compute-1.amazonaws.com
- ec2-12-123-456-222.compute-1.amazonaws.com
- ec2-12-123-456-333.compute-1.amazonaws.com
In the worst case, all hostnames in the broker cluster would be changed. So,
bootstrapAddresses() should be updated. How will you handle this case?
> Producer's Broker Discovery Interface
> -------------------------------------
>
> Key: KAFKA-1348
> URL: https://issues.apache.org/jira/browse/KAFKA-1348
> Project: Kafka
> Issue Type: Improvement
> Components: producer
> Reporter: Jay Bae
> Assignee: Jun Rao
>
> Producer has a property 'broker.list' static configuration. I need a
> requirement to be able to override this behavior such as Netflix Eureka
> Discovery module. Let me contribute and please add this to 0.8.1.1 release.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
