[
https://issues.apache.org/jira/browse/KAFKA-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225519#comment-14225519
]
Jun Rao commented on KAFKA-1790:
--------------------------------
The way that the controlled shutdown works now requires coordination btw the
broker to be shut down and the controller. So, the controlled shutdown has to
be initiated from the shutting down broker. By default, controlled shutdown is
enabled in the broker config. So on SIGTERM, the broker will wait until all
leaders are moved off itself before shutting itself down. Is there a particular
reason that you can't just SIGTERM the broker for doing the controlled shutdown?
> Remote controlled shutdown was removed
> --------------------------------------
>
> Key: KAFKA-1790
> URL: https://issues.apache.org/jira/browse/KAFKA-1790
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2
> Reporter: James Oliver
> Assignee: James Oliver
> Priority: Blocker
> Fix For: 0.8.2
>
>
> In core:
> kafka.admin.ShutdownBroker was removed, rendering remote controlled shutdowns
> impossible.
> A Kafka administrator needs to be able to perform a controlled shutdown
> without issuing a SIGTERM/SIGKILL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
