[
https://issues.apache.org/jira/browse/MAPREDUCE-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238683#comment-13238683
]
Hudson commented on MAPREDUCE-3353:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #738 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/738/])
MAPREDUCE-3353. Fixed commit msg to point to right jira. (Revision 1305458)
Result = ABORTED
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1305458
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
> Need a RM->AM channel to inform AMs about faulty/unhealthy/lost nodes
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-3353
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3353
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, mrv2, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Bikas Saha
> Fix For: 0.23.3
>
> Attachments: MAPREDUCE-3353-branch-0.23.patch,
> MAPREDUCE-3353-branch-0.23.patch, MAPREDUCE-3353-branch-0.23.patch,
> MAPREDUCE-3353-branch-0.23.patch, MAPREDUCE-3353-branch-0.23.patch,
> MAPREDUCE-3353-branch-0.23.patch, MAPREDUCE-3353-branch-0.23.patch
>
>
> When a node gets lost or turns faulty, AM needs to know about that event so
> that it can take some action like for e.g. re-executing map tasks whose
> intermediate output live on that faulty node.
--
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
