[
https://issues.apache.org/jira/browse/MAPREDUCE-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507730#comment-14507730
]
Rohith commented on MAPREDUCE-6329:
-----------------------------------
bq. Therefore I don't see how the RM could reasonably be expiring the node, nor
should the node be unregistering
Agree, practically thinking it won't be possible.
bq. Re-registration does not kill containers on the node
Without NM work-preserving restart enabled , RM should kill the running
containers on re-registration. IIRC, It is legacy behavior.
> Failure of start map task on NM cause job hang
> ----------------------------------------------
>
> Key: MAPREDUCE-6329
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6329
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Peng Zhang
> Attachments: syslog.tgz, yarn-app.log
>
>
> During rolling update of NM, AM start of container on NM failed.
> And then job hang there.
> Attach AM logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
