You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jeff Maxwell (JIRA)" <ji...@apache.org> on 2017/02/06 18:21:41 UTC
[jira] [Commented] (KAFKA-4264) kafka-server-stop.sh fails is Kafka
launched via kafka-server-start.sh
[ https://issues.apache.org/jira/browse/KAFKA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854484#comment-15854484 ]
Jeff Maxwell commented on KAFKA-4264:
-------------------------------------
The pull request [1984|https://github.com/apache/kafka/pull/1984] does not work as zookeeper's command line also includes {{kafka.logs.dir}}.
> kafka-server-stop.sh fails is Kafka launched via kafka-server-start.sh
> ----------------------------------------------------------------------
>
> Key: KAFKA-4264
> URL: https://issues.apache.org/jira/browse/KAFKA-4264
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Affects Versions: 0.10.0.1
> Environment: Tested in Debian Jessy
> Reporter: Alex Schmitz
> Priority: Trivial
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> kafka-server-stop.sh greps for the process ID to kill with the following:
> bq. PIDS=$(ps ax | grep -i 'kafka\.Kafka' | grep java | grep -v grep | awk '{print $1}')
> However, if Kafka is launched via the kafka-server-start.sh script, the process doesn't include kafka.Kafka, the grep fails to find the process, and it returns the failure message, No Kafka server to stop.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)