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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/07/16 16:50:48 UTC

[jira] [Reopened] (MAPREDUCE-5317) Stale files left behind for failed jobs

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

Jason Lowe reopened MAPREDUCE-5317:
-----------------------------------


This is causing some unit tests to hang/fail in hadoop-mapreduce-client-jobclient.  TestJobCleanup on 0.23, for example.  I missed the fact that when JobImpl short-circuits the FAIL_WAIT state and goes straight from RUNNING to FAIL_ABORT it is failing to send the committer event that will eventually trigger it to leave the FAIL_ABORT state.  That causes the AM to just hang in the FAIL_ABORT state.

Ravi, could you add that fix along with a test case for that scenario?  In the meantime I'll back out this change to fix the builds.
                
> Stale files left behind for failed jobs
> ---------------------------------------
>
>                 Key: MAPREDUCE-5317
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5317
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 3.0.0, 2.0.4-alpha, 0.23.8
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>             Fix For: 3.0.0, 2.3.0, 0.23.10
>
>         Attachments: MAPREDUCE-5317.branch-0.23.patch, MAPREDUCE-5317.branch-0.23.patch, MAPREDUCE-5317.patch, MAPREDUCE-5317.patch, MAPREDUCE-5317.patch, MAPREDUCE-5317.patch, MAPREDUCE-5317.patch
>
>
> Courtesy [~amar_kamat]!
> {quote}
> We are seeing _temporary files left behind in the output folder if the job
> fails.
> The job were failed due to hitting quota issue.
> I simply ran the randomwriter (from hadoop examples) with the default setting.
> That failed and left behind some stray files.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira