[
https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036359#comment-15036359
]
Aditya Auradkar commented on KAFKA-2310:
----------------------------------------
[~abiletskyi] - I see you submitted a pull request for this recently.
https://github.com/apache/kafka/pull/614/files
Can you actually elaborate on the reasoning behind this change a bit more? I
actually think we need a KIP to discuss this at least (given that it adds a new
config). I'm not really sure preventing a broker from becoming a controller
solves the underlying problem of a broker being overloaded.
> 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)
