Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9D22518629 for ; Sun, 1 Nov 2015 22:39:28 +0000 (UTC) Received: (qmail 77260 invoked by uid 500); 1 Nov 2015 22:39:28 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 77209 invoked by uid 500); 1 Nov 2015 22:39:28 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 77198 invoked by uid 99); 1 Nov 2015 22:39:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Nov 2015 22:39:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C22DE2C1F6E for ; Sun, 1 Nov 2015 22:39:27 +0000 (UTC) Date: Sun, 1 Nov 2015 22:39:27 +0000 (UTC) From: "sandflee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4051?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14984= 580#comment-14984580 ]=20 sandflee commented on YARN-4051: -------------------------------- Thanks Jason, sorry for just noticed your reply.=20 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=EF=BC=8Cshould we do that=EF=BC=9F > ContainerKillEvent is lost when container is In New State and is recover= ing > -------------------------------------------------------------------------= --- > > 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)