[
https://issues.apache.org/jira/browse/YARN-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589893#comment-14589893
]
Jason Lowe commented on YARN-3811:
----------------------------------
I agree with Jian that we probably don't need the not ready exception. I was
never a fan of it in the first place, as IMHO we should just avoid opening or
processing the client port until we've registered with the RM if it's really a
problem in practice. As Jian points out, I think the NMToken will cover the
cases where someone is trying to launch something they shouldn't be launching,
so I don't think we need to wait for the RM registration.
> NM restarts could lead to app failures
> --------------------------------------
>
> Key: YARN-3811
> URL: https://issues.apache.org/jira/browse/YARN-3811
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.7.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Critical
>
> Consider the following scenario:
> 1. RM assigns a container on node N to an app A.
> 2. Node N is restarted
> 3. A tries to launch container on node N.
> 3 could lead to an NMNotYetReadyException depending on whether NM N has
> registered with the RM. In MR, this is considered a task attempt failure. A
> few of these could lead to a task/job failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
