[
https://issues.apache.org/jira/browse/KAFKA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618034#comment-14618034
]
Joe Stein commented on KAFKA-2310:
----------------------------------
Hey [~jjkoshy] I had suggested to Andrii that it might make sense to make this
a new ticket. The old ticket (which I think we should close) had the idea that
we wanted to re-elect the controller. This would be problematic for what is
trying to solve based on what we have seen in the field. e.g. if you have 12
brokers and they are under heavy load then providing a way to "bounce the
controller" around is going to help if when it gets to a broker it can't
perform its responsibilities sufficiently. The consensus I have been able to
get from ops folks is that separating/isolating the controller onto two brokers
on two (for redundancy) lower end equipment solve the problem fully. Since this
is just another config I didn't think that i needed it KIP but honestly wasn't
100% sure otherwise would have already committed this feature. The purpose of
the patch for different versions is because I know a bunch of folks that are
going to take it for the version of kafka they are using and start using the
feature.
> 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)
