You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2010/05/01 01:35:53 UTC
[jira] Commented: (CHUKWA-483) bin/chukwa stop broken
[ https://issues.apache.org/jira/browse/CHUKWA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862928#action_12862928 ]
Eric Yang commented on CHUKWA-483:
----------------------------------
Looks like DestroyJavaVM thread was running. This means it should be able to terminate the program. Maybe it take longer than expected to clean up.
> bin/chukwa stop broken
> ----------------------
>
> Key: CHUKWA-483
> URL: https://issues.apache.org/jira/browse/CHUKWA-483
> Project: Hadoop Chukwa
> Issue Type: Bug
> Components: scripts
> Environment: Redhat EL 4.x, Java 1.6
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-483.1.patch, CHUKWA-483.threaddump.txt
>
>
> Since JIRA-468, bin/chukwa stop no longer works for collectors and agents. Can we change kill -1 back to kill -TERM?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.