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 "Chang Li (JIRA)" <ji...@apache.org> on 2015/06/10 23:01:02 UTC

[jira] [Updated] (MAPREDUCE-5003) AM recovery should recreate records for attempts that were incomplete

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

Chang Li updated MAPREDUCE-5003:
--------------------------------
    Attachment: MAPREDUCE-5003.1.patch

the AM hanging issue mentioned in MAPREDUCE-4992 no longer exists in current recover implementation. Moreover, current recovery implementation for task attempts will recover incomplete task attempts to killed state. So we no longer need to remove those incomplete task attempts for recovery. 

> AM recovery should recreate records for attempts that were incomplete
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5003
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5003
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am
>            Reporter: Jason Lowe
>            Assignee: Chang Li
>         Attachments: MAPREDUCE-5003.1.patch
>
>
> As discussed in MAPREDUCE-4992, it would be nice if the AM recovered task attempt entries for *all* task attempts launched by the prior app attempt even if those task attempts did not complete.  The attempts would have to be marked as killed or something similar to indicate it is no longer running.  Having records for the task attempts enables the user to see what nodes were associated with the attempts and potentially access their logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)