Return-Path: X-Original-To: apmail-samza-dev-archive@minotaur.apache.org Delivered-To: apmail-samza-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 5A43818709 for ; Tue, 3 Nov 2015 19:55:22 +0000 (UTC) Received: (qmail 20251 invoked by uid 500); 3 Nov 2015 19:55:21 -0000 Delivered-To: apmail-samza-dev-archive@samza.apache.org Received: (qmail 20190 invoked by uid 500); 3 Nov 2015 19:55:21 -0000 Mailing-List: contact dev-help@samza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@samza.apache.org Delivered-To: mailing list dev@samza.apache.org Received: (qmail 20177 invoked by uid 99); 3 Nov 2015 19:55:21 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2015 19:55:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0B4B81A0AE7 for ; Tue, 3 Nov 2015 19:55:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=chartbeat.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 48tEnGk3Yk6Y for ; Tue, 3 Nov 2015 19:55:09 +0000 (UTC) Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 66DBB444C5 for ; Tue, 3 Nov 2015 19:55:09 +0000 (UTC) Received: by qgad10 with SMTP id d10so22807312qga.3 for ; Tue, 03 Nov 2015 11:55:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chartbeat.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=WqI58DXcsX6StBi6V8ABMe9JzgXfV3dPAh/c1b0l9vU=; b=RAfi7qBCo80acZTHkRgpMJ7fWDtcNH9CcRBgVm+9uXuOLldpEe70TkSTmP/NezcYaX K/+zoOsqQk6RaFk1nkkQmqUJgcfcjL19exJG8xVckvTdfx81towMWycThA/lUOvywjcS 2kc7+7U9CTUBeSQusYobdCyrP3jLT50XDpTNI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:message-id:references:to; bh=WqI58DXcsX6StBi6V8ABMe9JzgXfV3dPAh/c1b0l9vU=; b=myToU8ebeqmNblPR56wB/iVsvDAITRWLZHK5Uff/V9OcKVvH5LREXpF/VHolovTSmr ufEdUa0p3y+UKeoRwQxx5nDNCKHvXT40AiSKeAei9B/nPw8R9RxVdYGE46tJDQCIGYqH d/UZ/VCuFV5JF96853gfUlG19uswWrmWlnnH6OojxUE+P1GL/J6mW6HuexFiD3BLVs/E q4ItSuiqFSgrANappU0DPy7EvvPxx6/YzKX5FVBW+YXjdOBFVBHpDTTwXF8r60usYnXC j5VgeA0cLaMldudmBrbiuEOoSl1u8/ewwfSEKG79/u5MgtBGgGuc1JEAmn5zXn7C5Ywz TdCg== X-Gm-Message-State: ALoCoQnrCi9CT/1MhIpxpWzBIfJoywdr3bq2E9s2QUdg8JsH+tR4tgwYBg1Qe7JtaF+gmC0HpOCu X-Received: by 10.140.150.139 with SMTP id 133mr42937381qhw.58.1446580508956; Tue, 03 Nov 2015 11:55:08 -0800 (PST) Received: from ip-192-168-152-149.ec2.internal (static-100-38-5-130.nycmny.fios.verizon.net. [100.38.5.130]) by smtp.gmail.com with ESMTPSA id o20sm10307620qki.42.2015.11.03.11.55.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Nov 2015 11:55:08 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_17C19C14-3771-4A8F-9B36-8FBE36746780"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Does Samza work with ResourceManager in HA? X-Pgp-Agent: GPGMail 2.5.1 From: Rick Mangi In-Reply-To: Date: Tue, 3 Nov 2015 14:55:06 -0500 Message-Id: References: <7426CD70-8E2C-4973-9FC8-F7E5C01055E2@chartbeat.com> To: dev@samza.apache.org X-Mailer: Apple Mail (2.2104) --Apple-Mail=_17C19C14-3771-4A8F-9B36-8FBE36746780 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Nope, we left it out. Rick > On Nov 3, 2015, at 11:04 AM, John Tipper = wrote: >=20 > Thanks Rick, much appreciated. Did you have to set = yarn.resourcemanager.hostname or can you leave this out? >=20 > Thanks, >=20 > John >=20 > ________________________________________ > From: Rick Mangi > Sent: 03 November 2015 15:46 > To: dev@samza.apache.org > Subject: Re: Does Samza work with ResourceManager in HA? >=20 > Hi John, >=20 > We just got this set up last week. I haven=92t fully tested the = failover but it certainly works for testing out our samza jobs on a = pretty large cluster. >=20 > All of the server names are fqdn in our live yarn-site.xml >=20 > Hope this helps, >=20 > Rick >=20 >=20 > > yarn.resourcemanager.ha.enabled > true > > > yarn.resourcemanager.ha.automatic-failover.enabled > true > > > yarn.resourcemanager.cluster-id > ops02 > > > yarn.resourcemanager.ha.rm-ids > rm1,rm2 > > > yarn.resourcemanager.hostname.rm1 > yarnmaster01 > > > yarn.resourcemanager.hostname.rm2 > yarnmaster02 > > > yarn.resourcemanager.webapp.address.rm1 > yarnmaster01:8088 > > > yarn.resourcemanager.webapp.address.rm2 > yarnmaster02:8088 > > > yarn.resourcemanager.zk-address > zk01:2181,zk02:2181,zk03:2181,zk04:2181,zk06:2181 lue> > > > yarn.resourcemanager.store.class > = org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateSto= re > >=20 > > yarn.resourcemanager.recovery.enabled > true > > > yarn.resourcemanager.zk-state-store.parent-path > /yarn_ops02_rmstore > >=20 >=20 >=20 >> On Nov 3, 2015, at 6:10 AM, John Tipper = wrote: >>=20 >>=20 >>=20 >> Does anyone have Samza working with resource manager in HA? If so, = what do I set yarn.resourcemanager.hostname to in yarn-site.xml? Can = anyone share a working yarn-site.xml please? >>=20 >>=20 >> If I set it to the first of my RMs, the the job submission works ok = if I submit the job from that RM and the RM is the active one. If the RM = machine that I run the job submission from is not active, I get = connection refused errors on port 8032. If I don't set it, I get errors = where run-job.sh tries to submit to 0.0.0.0:8032 >>=20 >>=20 >> Many thanks, >>=20 >>=20 >> John >=20 --Apple-Mail=_17C19C14-3771-4A8F-9B36-8FBE36746780 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJWOREaAAoJENgofZAtxzWQ0MMH/RALqX5KIB7JcK622J2Ok/9B WLpRLON2IC7zKSRKt6xhJUubg5KVHvu653f8V1CuBi57G6ydPRpRVbLQ2T+d96BI 9wjJQTO4M9x/wcPNE/t8FT2duFaJI7K5uar6e9dsm5lEIhnqF424hlJmKxh5QR6a pGbDD3hzSYOwjv40wgSWYAxOZawDaDfpHHXTE6fCZNW1NQQGOGsr7iDGUkCx4UqB 9Mhx5csEbeFrG8oJkdzY5KtzAF1dsAvCPrF+MeVklF/wZ9F7AfXGh9xIqr2Q1Qi7 loHvWiM/9bGeDqSDxaHoPQ/j17p9ljq4ddSVqN21sWfsVpBKhIfqXMn0lChLzv8= =KZOb -----END PGP SIGNATURE----- --Apple-Mail=_17C19C14-3771-4A8F-9B36-8FBE36746780--