[
https://issues.apache.org/jira/browse/KAFKA-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233313#comment-14233313
]
James Oliver commented on KAFKA-1790:
-------------------------------------
Hi [~junrao], the particular use case we were trying to satisfy is this:
A Kafka cluster is deployed on cloud infrastructure. Operations wants to modify
configurations and bounce boxes (keeping replication in mind so we don't
corrupt any topics), but the tool they use to interface with the cloud
infrastructure does not, at present, allow for sending signals to the
underlying processes. We are looking for a way to upgrade binaries / modify
configurations and have those changes reflected in our cluster by doing a
remote SIGTERM to do a controlled bounce.
Thinking about this in a more general sense, I don't think it's a good idea to
rely on Kafka for this ability when the root issue is the inability to send a
remote SIGTERM. That and the possible security issue is enough for me to call
this a no-go.
> 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)
