[
https://issues.apache.org/jira/browse/HADOOP-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724374#action_12724374
]
Sreekanth Ramakrishnan commented on HADOOP-6106:
------------------------------------------------
output from ant test-patch
{noformat}
[exec]
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] -1 javac. The applied patch generated 64 javac compiler
warnings (more than the trunk's current 124 warnings).
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] -1 release audit. The applied patch generated 271 release
audit warnings (more than the trunk's current 269 warnings).
[exec]
{noformat}
All test cases passed locally.
> 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.
