[
https://issues.apache.org/jira/browse/KAFKA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065670#comment-14065670
]
Sriharsha Chintalapani commented on KAFKA-1070:
-----------------------------------------------
[~jkreps] [~nehanarkhede]
I am working on this JIRA. Following the proposed design in the comments. I see
there might be a issue where
one of the broker configs have broker.id defined as 0 and another one doesn't
have broker.id. If the second broker started first we fetch a global sequence
id from zookeeper that starts with 0 and the next one has already have a
defined config we will use that in this case we have two brokers with same id.
Should we consider this case in which a kafka cluster's broker might have a
inconsistent config interms of broker.id.
Instead of using zookeeper for generating a global sequence number why
shouldn't we be using UUID and make brokerId Long type.
Thanks.
> Auto-assign node id
> -------------------
>
> Key: KAFKA-1070
> URL: https://issues.apache.org/jira/browse/KAFKA-1070
> Project: Kafka
> Issue Type: Bug
> Reporter: Jay Kreps
> Assignee: Sriharsha Chintalapani
> Labels: usability
>
> It would be nice to have Kafka brokers auto-assign node ids rather than
> having that be a configuration. Having a configuration is irritating because
> (1) you have to generate a custom config for each broker and (2) even though
> it is in configuration, changing the node id can cause all kinds of bad
> things to happen.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
