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 6F5E2100CA for ; Wed, 11 Feb 2015 08:02:12 +0000 (UTC) Received: (qmail 32132 invoked by uid 500); 11 Feb 2015 08:02:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 32092 invoked by uid 500); 11 Feb 2015 08:02:12 -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 32075 invoked by uid 99); 11 Feb 2015 08:02:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 08:02:12 +0000 Date: Wed, 11 Feb 2015 08:02:12 +0000 (UTC) From: "BOB (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-3173) start-yarn.sh script can't aware how many RM to be started. 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-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BOB updated YARN-3173: ---------------------- Summary: start-yarn.sh script can't aware how many RM to be started. (was: tart-yarn.sh script can't aware how many RM to be started.) > start-yarn.sh script can't aware how many RM to be started. > ------------------------------------------------------------ > > Key: YARN-3173 > URL: https://issues.apache.org/jira/browse/YARN-3173 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: BOB > Priority: Minor > > When config more than one RM, for example HA cluster, using the start-yarn.sh script to start yarn cluster,but the cluster only start up with one resourcemanager on the node which start-yarn.sh be executed. I think yarn should sense how many RMs been configured at the beginning, and start them all in start-yarn.sh script. -- This message was sent by Atlassian JIRA (v6.3.4#6332)