Return-Path: X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C070FD8A4 for ; Wed, 19 Sep 2012 00:43:03 +0000 (UTC) Received: (qmail 23544 invoked by uid 500); 19 Sep 2012 00:43:03 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 23464 invoked by uid 500); 19 Sep 2012 00:43:03 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 23450 invoked by uid 99); 19 Sep 2012 00:43:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 00:43:03 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=602bd7acd=criccomini@linkedin.com designates 69.28.149.81 as permitted sender) Received: from [69.28.149.81] (HELO esv4-mav05.corp.linkedin.com) (69.28.149.81) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 00:42:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1348015378; x=1379551378; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=6qz81ANo26bU+puaWe2vCz04fx6WUtqY9bgt/zJmEt4=; b=ISFhTvybyITa4WD0P+gf4M0vB/foezgzpaXouzYVKvUG02NemA6NP+LA +alfx1MB9gZ61dOOM43i32ysoAOkUBvc6kU4h11mCFyXYHBKHQ63zG6Sp oxYBMA5VA5zpOmJVtaXc9gOhTK4kEIJI4aiAtxJy5iPssm+riI69pSW5U 4=; X-IronPort-AV: E=Sophos;i="4.80,446,1344236400"; d="scan'208";a="25805484" Received: from ESV4-EXC02.linkedin.biz ([fe80::4d74:48bd:e0bd:13ee]) by esv4-cas02.linkedin.biz ([172.18.46.142]) with mapi id 14.01.0355.002; Tue, 18 Sep 2012 17:42:12 -0700 From: Chris Riccomini To: "mapreduce-dev@hadoop.apache.org" Subject: More than one RM in YARN? Thread-Topic: More than one RM in YARN? Thread-Index: Ac2V/2Gq7U1yS6pJScyflqEtbtoT7A== Date: Wed, 19 Sep 2012 00:42:12 +0000 Message-ID: <1B43C7411DB20E47AB0FB62E7262B80161D792B1@ESV4-EXC02.linkedin.biz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.247] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hey Guys, Is anyone running more than one RM on a YARN cluster (backed by ZK)? We're = looking at this, and I want to know if there's a standard way to do it. Are= people doing round robin DNS, load balancers, etc? Is it possible to confi= gure node managers to have a list of RMs rather than a single one? Thanks! Chris=