You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/03/03 11:07:24 UTC

[jira] [Resolved] (MAPREDUCE-2819) extend JobClient.runJob(JobConf) with the ability to take a timeout, so fail better during test runs

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved MAPREDUCE-2819.
---------------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 2.2.0

Obsoleted in YARN

> extend JobClient.runJob(JobConf) with the ability to take a timeout, so fail better during test runs
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2819
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2819
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Tests that submit jobs via JobClient hang until they are killed if something goes wrong in the back end -JobClient does not impose limits on how long runs should take, but JUnit does. If we had an overload of runJob() that took a timeout, JobClient could kill a job that was taking too long, extracting the stack trace and better diagnostics to the test reports. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)