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

Vinod Kumar Vavilapalli commented on MAPREDUCE-3889:
----------------------------------------------------

I just checked the code, the default is only for "FAILED" tasks. So, the error 
can happen even when there are failed tasks. 

What is the impact of this? Is it crashing the client? Seems like it from the 
code, in which case we'll need to fix it.

But the problem is that the client doesn't have a way of mapping TaskAttemptId 
to the ContainerIDs so that the log-urls can be constructed properly. So may be 
for the shorter term, we can disable the feature completely.
                
> job client tries to use /tasklog interface, but that doesn't exist anymore
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3889
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3889
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Thomas Graves
>            Priority: Critical
>
> if you specify  -Dmapreduce.client.output.filter=SUCCEEDED option when 
> running a job it tries to fetch task logs to print out on the client side 
> from a url like: 
> http://nodemanager:8080/tasklog?plaintext=true&attemptid=attempt_1329857083014_0003_r_000000_0&filter=stdout
> It always errors on this request with: Required param job, map and reduce
> We saw this error when using distcp and the distcp failed. I'm not sure if it 
> is mandatory for distcp or just informational purposes.  I'm guessing the 
> latter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to