hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering
Date Sun, 01 Nov 2015 22:39:27 GMT

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

sandflee commented on YARN-4051:
--------------------------------

Thanks Jason,  sorry for just noticed your reply. 

It's more reasonable to let others retry before nm recovered containers.
1, For AM stopContainer request ,  we could it simply like startContainers
2, For RM finish application or complete container request,  let RM retry, seems a little
complicated,should we do that?

> ContainerKillEvent is lost when container is  In New State and is recovering
> ----------------------------------------------------------------------------
>
>                 Key: YARN-4051
>                 URL: https://issues.apache.org/jira/browse/YARN-4051
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: sandflee
>            Assignee: sandflee
>            Priority: Critical
>         Attachments: YARN-4051.01.patch, YARN-4051.02.patch, YARN-4051.03.patch
>
>
> As in YARN-4050, NM event dispatcher is blocked, and container is in New state, when
we finish application, the container still alive even after NM event dispatcher is unblocked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message