Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1096648266.1245996427577.JavaMail.jira@brutus>
Date: Thu, 25 Jun 2009 23:07:07 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6106) Provide an option in
 ShellCommandExecutor to timeout commands that do not complete within a
 certain amount of time.
In-Reply-To: <617214802.1245927547649.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hemanth Yamijala commented on HADOOP-6106:
------------------------------------------

+1 for the changes.

> Provide an option in ShellCommandExecutor to timeout commands that do not complete within a certain amount of time.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6106
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6106
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>            Reporter: Hemanth Yamijala
>            Assignee: Sreekanth Ramakrishnan
>         Attachments: HADOOP-6106-1.patch, HADOOP-6106-2.patch, HADOOP-6106.patch, mapred-211-common-3.patch
>
>
> In MAPREDUCE-211 we came across a need to provide an option to timeout commands launched via the ShellCommandExecutor. The use case is for the health check script being developed in MAPREDUCE-211. We would like the TaskTracker thread to not be blocked by a problematic script or in instances where fork()+exec() has hung (which apparently has been observed in large clusters).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.