[
https://issues.apache.org/jira/browse/KAFKA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228073#comment-13228073
]
Neha Narkhede commented on KAFKA-293:
-------------------------------------
I like the meta.properties approach, better than Zookeeper's approach to its
configuration. It is certainly more involved, but has some advantages, like Jay
mentioned. Just one thing to be careful about if we use the ephemeral
sequential node feature in ZK -
A kafka broker asks zookeeper to create an ephemeral sequential node, and the
create() succeeds on the server but the server crashes before returning the
name of the node to kafka. When the kafka broker reconnects, its session is
still valid and, thus, the node is not removed. The implication is that it is
difficult for the Kafka broker to know if its node was created or not.
One way of handling recoverable errors while using sequential ephemeral nodes
is that we can simply assume that the node wasn't created and create another
one. This means that the ids will not be contiguous.
> Allow to configure all broker ids at once similar to how zookeeper handles
> server ids
> -------------------------------------------------------------------------------------
>
> Key: KAFKA-293
> URL: https://issues.apache.org/jira/browse/KAFKA-293
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.7
> Reporter: Thomas Dudziak
>
> Zookeeper allows to specify all server ids in the same configuration
> (https://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_configuration)
> which has the benefit that the configuration file is the same for all
> zookeeper instances. A similar approach for Kafka would be quite useful, e.g.
> brokerid.1=<host 1>
> brokerid.2=<host 2>
> etc.
> It'd still require per-instance configuration (myid file in the zookeeper
> case) but that can be created separately (e.g. by the deployment tool used).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
