[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Fix Version/s: (was: 0.10.0.1) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp > :/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/aopalliance-repackaged-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/argparse4j-0.5.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-api-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-file-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-json-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-runtime-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/guava-18.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-api-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-locator-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-utils-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-annotations-2.6.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-core-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-databind-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-base-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-json-provider-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-module-jaxb-annotations-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javassist-3.18.2-GA.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.annotation-api-1.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.servlet-api-3.1.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.ws.rs-api-2.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-client-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-common-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-core-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-guava-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-media-jaxb-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-server-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-continuation-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-http-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-io-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-security-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-server-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlet-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlets-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-util-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jopt-simple-4.9.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-test-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka > ``` >
[jira] [Issue Comment Deleted] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Comment: was deleted (was: KAFKA-4297.solution2.patch: I modified 'kafka\.Kafka' to 'kafkaServer-gc' in 'kafka-server-stop.sh') > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Attachment: (was: KAFKA-4297.solution1.patch) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Issue Comment Deleted] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Comment: was deleted (was: KAFKA-4297.solution1.patch: I added '-Dkafka.server' option in running command and modified stop script.) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Attachment: (was: KAFKA-4297.solution2.patch) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Attachment: KAFKA-4297.solution2.patch KAFKA-4297.solution2.patch: I modified 'kafka\.Kafka' to 'kafkaServer-gc' in 'kafka-server-stop.sh' > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > Attachments: KAFKA-4297.solution1.patch, KAFKA-4297.solution2.patch > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Comment Edited] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15570754#comment-15570754 ] Mabin Jeong edited comment on KAFKA-4297 at 10/13/16 4:03 AM: -- KAFKA-4297.solution1.patch: I added '-Dkafka.server' option in running command and modified stop script. was (Author: mabin): I added '-Dkafka.server' option in running command and modified stop script. > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > Attachments: KAFKA-4297.solution1.patch, KAFKA-4297.solution2.patch > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Attachment: KAFKA-4297.solution1.patch I added '-Dkafka.server' option in running command and modified stop script. > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > Attachments: KAFKA-4297.solution1.patch > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Status: Open (was: Patch Available) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > Attachments: KAFKA-4297.solution1.patch > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Issue Comment Deleted] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Comment: was deleted (was: I added '-Dkafka.server' option in running command and modified stop script.) > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > Attachments: KAFKA-4297.solution1.patch > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Status: Patch Available (was: Open) I added '-Dkafka.server' option in running command and modified stop script. > Cannot Stop Kafka with Shell Script > --- > > Key: KAFKA-4297 > URL: https://issues.apache.org/jira/browse/KAFKA-4297 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.0.1 > Environment: CentOS 6.7 >Reporter: Mabin Jeong >Priority: Critical > Labels: easyfix > Fix For: 0.10.0.1 > > > If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. > That command showed this message: > ``` > No kafka server to stop > ``` > This bug is caused that command line is too long like this. > ``` > /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server > -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 > -XX:+DisableExplicitGC -Djava.awt.headless=true > -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc > -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka > -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties > -cp >
[jira] [Updated] (KAFKA-4297) Cannot Stop Kafka with Shell Script
[ https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mabin Jeong updated KAFKA-4297: --- Description: If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. That command showed this message: ``` No kafka server to stop ``` This bug is caused that command line is too long like this. ``` /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+DisableExplicitGC -Djava.awt.headless=true -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties -cp :/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/aopalliance-repackaged-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/argparse4j-0.5.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-api-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-file-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-json-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-runtime-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/guava-18.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-api-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-locator-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-utils-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-annotations-2.6.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-core-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-databind-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-base-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-json-provider-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-module-jaxb-annotations-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javassist-3.18.2-GA.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.annotation-api-1.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.servlet-api-3.1.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.ws.rs-api-2.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-client-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-common-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-core-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-guava-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-media-jaxb-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-server-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-continuation-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-http-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-io-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-security-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-server-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlet-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlets-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-util-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jopt-simple-4.9.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-test-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka ``` but that is not all command line. Full command line is this. ``` /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+DisableExplicitGC -Djava.awt.headless=true -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Dcom.sun.management.jmxremote
[jira] [Created] (KAFKA-4297) Cannot Stop Kafka with Shell Script
Mabin Jeong created KAFKA-4297: -- Summary: Cannot Stop Kafka with Shell Script Key: KAFKA-4297 URL: https://issues.apache.org/jira/browse/KAFKA-4297 Project: Kafka Issue Type: Bug Affects Versions: 0.10.0.1 Environment: CentOS 6.7 Reporter: Mabin Jeong Priority: Critical Fix For: 0.10.0.1 If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. That command showed this message: ``` No kafka server to stop ``` This bug is caused that command line is too long like this. ``` /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+DisableExplicitGC -Djava.awt.headless=true -Xloggc:/home/bbdev/Amasser/var/log/kafka/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dkafka.logs.dir=/home/bbdev/Amasser/var/log/kafka -Dlog4j.configuration=file:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../config/log4j.properties -cp :/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/aopalliance-repackaged-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/argparse4j-0.5.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-api-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-file-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-json-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/connect-runtime-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/guava-18.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-api-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-locator-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/hk2-utils-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-annotations-2.6.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-core-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-databind-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-base-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-jaxrs-json-provider-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jackson-module-jaxb-annotations-2.6.3.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javassist-3.18.2-GA.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.annotation-api-1.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.inject-2.4.0-b34.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.servlet-api-3.1.0.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/javax.ws.rs-api-2.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-client-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-common-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-container-servlet-core-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-guava-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-media-jaxb-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jersey-server-2.22.2.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-continuation-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-http-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-io-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-security-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-server-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlet-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-servlets-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jetty-util-9.2.15.v20160210.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/jopt-simple-4.9.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka/bin/../libs/kafka_2.11-0.10.0.1-test-sources.jar:/home/bbdev/Amasser/etc/alternatives/kafka ``` but that is not all command line. Full command line is this. ``` /home/bbdev/Amasser/etc/alternatives/jre/bin/java -Xms1G -Xmx5G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35