[
https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553429#comment-14553429
]
Joel Koshy commented on KAFKA-1778:
-----------------------------------
I may be missing some detail, but (a), (b), (c) don't quite fit the scenario I
was asking about:
Even if all brokers know that a specific broker is supposed to become the
preferred controller. What happens if that preferred controller is about to
become the controller but crashes before it can update the /controller path in
ZooKeeper. No further zookeeper watches will be triggered.
Also, can we avoid the message from current controller to the preferred
controller by having all brokers just watch the admin/next_controller znode?
Under changes in election code - (a) did you mean that brokers should watch
admin/next_controller znode (and not ready-to-serve-as-controller znode)?
> 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)
