kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vahid Hashemian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4931) stop script fails due 4096 ps output limit
Date Mon, 10 Jul 2017 19:02:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080885#comment-16080885
] 

Vahid Hashemian commented on KAFKA-4931:
----------------------------------------

[~tombentley] What exactly has the 4096 character limit? Is it the output of {{ps ax}}? Or
something else?
For me in an Ubuntu machine, the output of {{ps ax}} is over 50K long, and the stop script
works fine.

> stop script fails due 4096 ps output limit
> ------------------------------------------
>
>                 Key: KAFKA-4931
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4931
>             Project: Kafka
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 0.10.2.0
>            Reporter: Amit Jain
>            Assignee: Tom Bentley
>            Priority: Minor
>              Labels: patch-available
>
> When run the script: bin/zookeeper-server-stop.sh fails to stop the zookeeper server
process if the ps output exceeds 4096 character limit of linux. I think instead of ps we can
use ${JAVA_HOME}/bin/jps -vl | grep QuorumPeerMain  it would correctly stop zookeeper process.
Currently we are using kill 
> PIDS=$(ps ax | grep java | grep -i QuorumPeerMain | grep -v grep | awk '{print $1}')



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message