hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@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.
Date Fri, 26 Jun 2009 06:07:07 GMT

    [ 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.


Mime
View raw message