hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3349) No rack-name logged in JobHistory for unsuccessful tasks
Date Wed, 21 Dec 2011 02:59:30 GMT

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

Amar Kamat commented on MAPREDUCE-3349:
---------------------------------------

Sid,
Does it makes sense to port MAPREDUCE-778 to 0.23? Its an important feature and affects only
Rumen.
                
> No rack-name logged in JobHistory for unsuccessful tasks
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-3349
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3349
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Devaraj K
>            Priority: Blocker
>              Labels: hostname, rackname, rumen, unsuccessful
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3349-v1.11.patch, MAPREDUCE-3349-v1.4.patch, MAPREDUCE-3349-v1.6.patch,
MAPREDUCE-3349.patch
>
>
> Found this while running jobs on a cluster with [~Karams].
> This is because TaskAttemptUnsuccessfulCompletionEvent history record doesn't have a
rack field.

--
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