hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7722) Support a stop command in ShellCommandExecutor
Date Wed, 05 Oct 2011 21:38:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121502#comment-13121502

Hadoop QA commented on HADOOP-7722:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/268//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/268//console

This message is automatically generated.
> Support a stop command in ShellCommandExecutor 
> -----------------------------------------------
>                 Key: HADOOP-7722
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7722
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Hitesh Shah
>            Priority: Minor
>             Fix For: 0.23.0
>         Attachments: HADOOP-7722.1.patch
> Add a stop function call to Shell so as to either stop the process from getting started
if not already done so or destroy the process if it already has started. 
> Context of usage: 
> There can be race conditions when trying to kill an execution as the shell::execute call
is blocking and using the getProcess call is not a  feasible option as there can be a delay
between the execute call and when the process object is actually created ( after which it
can be used to kill the running sub-process ). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message