[
https://issues.apache.org/jira/browse/KAFKA-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233333#comment-14233333
]
Joel Koshy commented on KAFKA-1790:
-----------------------------------
One possibility is to allow sending ControlledShutdownRequest to any broker. If
a broker is not the controller the it can interpret the request as a request to
shutdown itself in which case the broker issues the ControlledShutdownRequest
to the controller. The tricky part is that the original shutdown request needs
to be put into a purgatory and the response needs to be sent before shutting
down the socket server. Also, KafkaApis which handles the original shutdown
request needs to be able to trigger the shutdown sequence. This can be done via
some condition variable or other mechanism that it can signal after a
successful controlled shutdown response.
> 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)
