[
https://issues.apache.org/jira/browse/HADOOP-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725499#action_12725499
]
Hemanth Yamijala commented on HADOOP-6106:
------------------------------------------
I had a chat with Owen and Giri about how to get this dependency jar into the
HDFS and MapReduce sub projects. Basically the current school of thought (until
IVY is fixed to automate this) is to take the latest built binary from Hudson
(http://hudson.zones.apache.org/hudson/view/Hadoop/job/Hadoop-Common-trunk/)
and commit it to the HDFS and MapReduce sub projects - making an entry in
changes.txt referencing this JIRA.
We are running HDFS and MapReduce unit tests with the latest jar to make sure
tests work fine. Once that's done, we'll commit it.
> 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
> Fix For: 0.21.0
>
> 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.
