Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 4 Oct 2011 20:42:34 +0000 (UTC)
From: "Hitesh Shah (Created) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <275177520.9134.1317760954086.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HADOOP-7722) Support a stop command in
 ShellCommandExecutor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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