[
https://issues.apache.org/jira/browse/KAFKA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922649#comment-13922649
]
Martin Kleppmann commented on KAFKA-1189:
-----------------------------------------
This happens if the broker is started with {{./bin/kafka-server-start.sh
-daemon config/server.properties}} — it seems that {{nohup}} swallows the
SIGINT signal. Changing the shutdown script to SIGTERM fixes the problem.
> kafka-server-stop.sh doesn't stop broker
> ----------------------------------------
>
> Key: KAFKA-1189
> URL: https://issues.apache.org/jira/browse/KAFKA-1189
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Affects Versions: 0.8.0
> Environment: RHEL 6.4 64bit, Java 6u35
> Reporter: Bryan Baugher
> Priority: Minor
> Labels: newbie
> Attachments: KAFKA-1189.patch
>
>
> Just before the 0.8.0 release this commit[1] changed the signal in the
> kafka-server-stop.sh script from SIGTERM to SIGINT. This doesn't seem to stop
> the broker. Changing this back to SIGTERM (or -15) fixes the issues.
> [1] -
> https://github.com/apache/kafka/commit/51de7c55d2b3107b79953f401fc8c9530bd0eea0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
