hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3889) job client tries to use /tasklog interface, but that doesn't exist anymore
Date Fri, 08 Jun 2012 11:23:23 GMT

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

Devaraj K commented on MAPREDUCE-3889:
--------------------------------------

By default this issue is coming from the Job client for all the Jobs which has any failed
tasks or if the profiling is enabled(MAPREDUCE-4294).

When the 400 error prints on the console/job client side, the users may think that due to
this error job got failed and starts investigating on this instead of checking the original
cause for job failure. 


As Vinod mentioned, I feel it is better to remove/disable this feature as TaskLogServlet support
is already removed and there is no info in the Job Client/NM for mapping from task attempt
to container id.

Is there any other way to go ahead for this issue?
                
> 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

        

Mime
View raw message