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 6AA1A101B5 for ; Sat, 19 Oct 2013 00:07:42 +0000 (UTC) Received: (qmail 56852 invoked by uid 500); 19 Oct 2013 00:07:42 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 56794 invoked by uid 500); 19 Oct 2013 00:07:42 -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 56786 invoked by uid 99); 19 Oct 2013 00:07:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Oct 2013 00:07:42 +0000 Date: Sat, 19 Oct 2013 00:07:42 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms 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-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799675#comment-13799675 ] Vinod Kumar Vavilapalli commented on YARN-884: ---------------------------------------------- bq. Vinod Kumar Vavilapalli, partly agree with you that they are two different knobs. However, at least in the current implementation, restarting an NM cleans up all the containers on it (correct me if I am wrong) including the AM. In that scenario, having a higher value for AM_EXPIRY will only delay starting the AM. No? That is just a temporary artifact of us not having work-preserving restart. That shouldn't change our meaning of long term configuration properties. > AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms > ------------------------------------------------------------------------------------------- > > Key: YARN-884 > URL: https://issues.apache.org/jira/browse/YARN-884 > Project: Hadoop YARN > Issue Type: Improvement > Affects Versions: 2.0.4-alpha > Reporter: Karthik Kambatla > Assignee: Karthik Kambatla > Labels: configuration > Attachments: yarn-884-1.patch > > > As the AM can't outlive the NM on which it is running, it is a good idea to disallow setting the am.liveness-monitor.expiry-interval-ms to a value higher than nm.liveness-monitor.expiry-interval-ms -- This message was sent by Atlassian JIRA (v6.1#6144)