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 BAD8917A3D for ; Sat, 25 Apr 2015 13:42:40 +0000 (UTC) Received: (qmail 5634 invoked by uid 500); 25 Apr 2015 13:42:38 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 5582 invoked by uid 500); 25 Apr 2015 13:42:38 -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 5571 invoked by uid 99); 25 Apr 2015 13:42:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Apr 2015 13:42:38 +0000 Date: Sat, 25 Apr 2015 13:42:38 +0000 (UTC) From: "sandflee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time 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-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-3518: --------------------------- Summary: default rm/am expire interval should not less than default resourcemanager connect wait time (was: default rm/am expire interval should less than default resourcemanager connect wait time) > default rm/am expire interval should not less than default resourcemanager connect wait time > -------------------------------------------------------------------------------------------- > > Key: YARN-3518 > URL: https://issues.apache.org/jira/browse/YARN-3518 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager, resourcemanager > Reporter: sandflee > > take am for example, if am can't connect to RM, after am expire (600s), RM relaunch am, and there will be two am at the same time util resourcemanager connect max wait time(900s) passed. > DEFAULT_RESOURCEMANAGER_CONNECT_MAX_WAIT_MS = 15 * 60 * 1000; > DEFAULT_RM_AM_EXPIRY_INTERVAL_MS = 600000; > DEFAULT_RM_NM_EXPIRY_INTERVAL_MS = 600000; -- This message was sent by Atlassian JIRA (v6.3.4#6332)