[
https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616401#comment-14616401
]
Andrii Biletskyi commented on KAFKA-2310:
-----------------------------------------
[~jjkoshy] yes, it might be a duplicate. Although we didn't agree there what we
want to do - force re-elect command or do it via config (as Joe mentioned in
his comment). This patch is the implementation of the latter one.
Not sure what should we do though - duplicate, link or maybe convert as
sub-task of the KAFKA-1778.
> Add config to prevent broker becoming controller
> ------------------------------------------------
>
> Key: KAFKA-2310
> URL: https://issues.apache.org/jira/browse/KAFKA-2310
> Project: Kafka
> Issue Type: Bug
> Reporter: Andrii Biletskyi
> Assignee: Andrii Biletskyi
> Attachments: KAFKA-2310.patch, KAFKA-2310_0.8.1.patch,
> KAFKA-2310_0.8.2.patch
>
>
> The goal is to be able to specify which cluster brokers can serve as a
> controller and which cannot. This way it will be possible to "reserve"
> particular, not overloaded with partitions and other operations, broker as
> controller.
> Proposed to add config _controller.eligibility_ defaulted to true (for
> backward compatibility, since now any broker can become a controller)
> Patch will be available for trunk, 0.8.2 and 0.8.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
