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 "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/11/06 09:47:20 UTC

[jira] [Commented] (MAPREDUCE-4362) If possible, we should get back the feature of propagating task logs back to JobClient

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814717#comment-13814717 ] 

Sandy Ryza commented on MAPREDUCE-4362:
---------------------------------------

Attaching a rebased patch with only the MR changes, using the URL format supported by YARN-649.  It's not ready - when I try to test it out on a pseudodistributed cluster, the NM is failing to locate the container requested by the MR client.

I don't have a ton of bandwidth to work on this at the moment, so anyone should feel free to pick it up.

> If possible, we should get back the feature of propagating task logs back to JobClient
> --------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4362
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4362
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, mrv2
>    Affects Versions: 2.0.0-alpha
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-4362.patch, MAPREDUCE-4362.patch
>
>
> MAPREDUCE-3889 removed the code which was trying to pull from /tasklog. We should see if it is possible to get back the feature.



--
This message was sent by Atlassian JIRA
(v6.1#6144)