[
https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692289#comment-14692289
]
Guozhang Wang commented on KAFKA-1778:
--------------------------------------
Chiming in late here, I think we are actually discussing two different, though
somewhat overlapped issues:
1. When a controller is in bad state but not resigning, or if we just want to
move controllers programmatically (i.e. not through deleting znode or bouncing
broker), we want to trigger a re-election, and potentially enforce a certain
broker to be the new controller during the re-election so that the whole
cluster can still move on without losing one broker.
2. For isolating load scenarios, we want to start a broker while indicating it
to be the controller candidate or not. Controller elections will only be
triggered among the candidates.
Per the JIRA title suggests, I think we are targeting on the first issue, for
which the motivation is mainly operation convenience; hence the solution for
the second issue may not really be preferred since it still does not allow SREs
to trigger a new election ([~charmalloc] corrects me if I am wrong).
> 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)
