[
https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550019#comment-14550019
]
Joel Koshy commented on KAFKA-1778:
-----------------------------------
Jun - I think this is more for convenience/debugging and such. Right now there
is no easy way to force a broker to become the controller.
Joe, since you filed this, you may be able to give some use case that you had
in mind.
Abhishek, what would happen if the current controller A resigns and another
broker B is pinned and about to become the new controller, but crashes before
it can become the controller. Other brokers would not participate in controller
reelection. So they should probably also watch the broker registrations so they
know if the pinned controller goes down then they should proceed to participate
in controller reelection anyway (to avoid a situation where you have no
controller).
> 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)
