hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3889) job client tries to use /tasklog interface, but that doesn't exist anymore
Date Wed, 20 Jun 2012 21:43:42 GMT

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

Robert Joseph Evans updated MAPREDUCE-3889:
-------------------------------------------

          Resolution: Fixed
       Fix Version/s: 3.0.0
                      2.0.1-alpha
                      0.23.3
    Target Version/s: 2.0.0-alpha, 0.23.3, 3.0.0  (was: 0.23.3, 2.0.0-alpha, 3.0.0)
              Status: Resolved  (was: Patch Available)

Thanks Devaraj,

Keep up the good work.  I put this into branch-0.23, branch-2, and trunk.
                
> 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, 2.0.1-alpha, 3.0.0
>            Reporter: Thomas Graves
>            Assignee: Devaraj K
>            Priority: Critical
>             Fix For: 0.23.3, 2.0.1-alpha, 3.0.0
>
>         Attachments: MAPREDUCE-3889.patch, MAPREDUCE-3889.patch
>
>
> 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