[
https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561833#comment-14561833
]
Abhishek Nigam commented on KAFKA-1778:
---------------------------------------
Joel,
What I was proposing was that all the brokers will watch the
ready-to-serve-as-controller ephemeral node. In the scenario outlined where the
preferred controller dies after the election is over but before it can write to
the /controller node all the brokers will get this notification. Then there
will be another round of elections in that case.
The controller is the one which pulls from /admin/next_controller persistent
zookeeper node and also keeps a watch on it. If it detects this has been
changed and the chosen broker id is different from it it will start the
preferred controller move process.
"Also, can we avoid the message from current controller to the preferred
controller by having all brokers just watch the admin/next_controller znode?"
This is definitely a better approach where zookeeper node can be used to
achieve this messaging.
Jun,
In my opinion static assignment suffers from some issues where if the
pre-determined controller goes down what happens or runs into any issues what
happens.
> Create new re-elect controller admin function
> ---------------------------------------------
>
> Key: KAFKA-1778
> URL: https://issues.apache.org/jira/browse/KAFKA-1778
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Joe Stein
> Assignee: Abhishek Nigam
> Fix For: 0.8.3
>
>
> kafka --controller --elect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
