[
https://issues.apache.org/jira/browse/MAPREDUCE-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173809#comment-13173809
]
Siddharth Seth commented on MAPREDUCE-3349:
-------------------------------------------
bq.
Does it makes sense to port MAPREDUCE-778 to 0.23? Its an important feature and
affects only Rumen.
Don't have enough context on how Rumen is currently used and what changes with
778. Seems like a new feature, and since it affects only Rumen, I don't see any
issue with it being merged into 23. However, it's best if the RM or someone
with more context takes that call.
> 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