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 49B7519AD2 for ; Tue, 8 Mar 2016 01:42:41 +0000 (UTC) Received: (qmail 93004 invoked by uid 500); 8 Mar 2016 01:42:41 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 92912 invoked by uid 500); 8 Mar 2016 01:42:40 -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 92881 invoked by uid 99); 8 Mar 2016 01:42:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2016 01:42:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B59AD2C1F58 for ; Tue, 8 Mar 2016 01:42:40 +0000 (UTC) Date: Tue, 8 Mar 2016 01:42:40 +0000 (UTC) From: "Jun Gong (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4770) Auto-restart of containers should work across NM restarts. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184195#comment-15184195 ] Jun Gong commented on YARN-4770: -------------------------------- Thanks [~vinodkv] for reporting the issue. The patch in YARN-3998 should have handled this case. {quote} The relaunch feature needs to work across NM restarts, so we should save the retry-context and policy per container into the state-store and reload it for continue relaunching after NM restart. {quote} As [~vvasudev] said, "The container retry policy details are already stored in the state-store as part of the ContainerLaunchContext", so we do not need care it. {quote} We should also handle restarting of any containers that may have crashed during the NM reboot. {quote} If container crashed during the NM reboot, container would transit to RELAUNCHING state. I will check it again. > Auto-restart of containers should work across NM restarts. > ---------------------------------------------------------- > > Key: YARN-4770 > URL: https://issues.apache.org/jira/browse/YARN-4770 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Vinod Kumar Vavilapalli > Assignee: Vinod Kumar Vavilapalli > > See my comment [here|https://issues.apache.org/jira/browse/YARN-3998?focusedCommentId=15133367&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15133367] on YARN-3998. Need to take care of two things: > - The relaunch feature needs to work across NM restarts, so we should save the retry-context and policy per container into the state-store and reload it for continue relaunching after NM restart. > - We should also handle restarting of any containers that may have crashed during the NM reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)