Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E00B0200CE0 for ; Thu, 27 Jul 2017 02:24:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DE5F4169DCA; Thu, 27 Jul 2017 00:24:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0812A169DC9 for ; Thu, 27 Jul 2017 02:24:37 +0200 (CEST) Received: (qmail 29226 invoked by uid 500); 27 Jul 2017 00:24:37 -0000 Mailing-List: contact user-help@livy.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@livy.incubator.apache.org Delivered-To: mailing list user@livy.incubator.apache.org Received: (qmail 29216 invoked by uid 99); 27 Jul 2017 00:24:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2017 00:24:37 +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 B89641A0656 for ; Thu, 27 Jul 2017 00:24:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.15 X-Spam-Level: X-Spam-Status: No, score=-0.15 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HpKYqxze8HJz for ; Thu, 27 Jul 2017 00:24:34 +0000 (UTC) Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3661061B4D for ; Thu, 27 Jul 2017 00:24:34 +0000 (UTC) Received: by mail-pf0-f179.google.com with SMTP id d67so8893536pfc.0 for ; Wed, 26 Jul 2017 17:24:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=XBLT6GfT4lKR0yomTUm0VsvwYcYWopBKwIF76UdsKaI=; b=kkWfjgYXj+1hIv87vJt92S+0ho61N0MlGR+ISzjaqRKA7IPOJCE/2nAqGiHa4rK3As geW6GIgpUTg0+RDK+3BxSDoGbw9HU9B4ornxT9vMVmNSaGJGYX/p7d9jT3QV2rBnHY5Y AjUtkNH2o9SD4WSYzDTuWgibVQllxZlR5NPrCM5zo+HqYfnDqWF3Ybo1mwWjc3O+4wUS BLLo441esXmQOFyx9mdX7/Ev+q50hiSPwuQ9R4mUSvUGMFgUmTf7mRfvBT1Ch1lTDYjs WyAOnNeb3vPZIOP9JtxTYlewDJ3vj+HqDmFa9GPyTUK+g5B0MDM5CkebhJbbHH4ICVsc QHPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=XBLT6GfT4lKR0yomTUm0VsvwYcYWopBKwIF76UdsKaI=; b=U13FaFJXuAZHn1b2JlPRh357LH7rziSeoCN5fCYvlsqbK7xqOHTjtdEkR4Z5Pi83hZ vggXk3Cd5jq6UPQG5x9JSDOmt75lqRiRPL5+GOSC3Hk+2RuDIVMuccUwPvVygfrKn4/t 5akRrAG/wvbfUXXiMgCg2pzpHfTKjXk9GFkIWDqXpQWD3PhJm/S6MTAXJNTsgyCb5ScZ Ix9ECpTlLzcxJWFvhO0TC/+dTEnwr8QC9HV2W6B7DwmiQvdecSViMBUbbLhauw6QnV35 DVfXrWbk1sB7rvI1PP777Rq6ovIUp43qsIY66LIlTP3l4nlIhodJXDzYZcwny6rqeTAc SRYw== X-Gm-Message-State: AIVw1128VPf572rG9yUAjxyEeqLrUkFHPUudwXZpmFE073gTZB6b3kq0 tlJTpfcMWGtKqisRVWY= X-Received: by 10.84.134.131 with SMTP id 3mr2542040plh.378.1501115072284; Wed, 26 Jul 2017 17:24:32 -0700 (PDT) Received: from [192.168.0.189] ([222.165.72.2]) by smtp.gmail.com with ESMTPSA id o4sm30311709pga.47.2017.07.26.17.24.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 17:24:31 -0700 (PDT) From: Vivek Suvarna Content-Type: multipart/alternative; boundary=Apple-Mail-D807AF7D-E0D9-472B-AA34-D61F4AA7057D Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Thu, 27 Jul 2017 08:24:28 +0800 Subject: Re: Multiple Livy instances and load balancing Message-Id: <3C81AB9F-924D-4FB4-8F8B-C8A0E7EB2495@gmail.com> References: <89AF9504-4607-4B41-BA03-CF0BD9635653@yahoo.co.in> <06D022FF-6511-422C-BCD5-2F5EFA9EF5FD@yahoo.co.in> In-Reply-To: To: user@livy.incubator.apache.org X-Mailer: iPhone Mail (14F89) archived-at: Thu, 27 Jul 2017 00:24:39 -0000 --Apple-Mail-D807AF7D-E0D9-472B-AA34-D61F4AA7057D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks Meisam.=20 Is this code in github?=20 Is there a PR for this? Regards Vivek Sent from my iPhone > On 27 Jul 2017, at 12:51 AM, Meisam Fathi wrote: >=20 > Hi Vivek, >=20 > We are running multiple instances of Livy on our clusters. Our users can c= reate and access jobs on any of the Livy instances. >=20 > To answer your particular question >=20 > 1. Is this feature available in the 0.3 release? No. The feature is not av= ailable out of the box=E2=80=93we modified Livy to add this feature.=20 > 2. How would I name/number the multiple instances I bring up? The load bal= ancer knows all the instances. Users only interact with the load balancer. > 3. How does one load balance and send requests across the multiple instanc= es? Livy instances do not know that requests come from a load balancer. Each= processes requests it receives and updates a shared "session store", which w= e implemented on top of ZooKeeper. > 4. Does Livy have a heartbeat mechanism to understand which or how many in= stances are up? No. There is a heartbeat mechanism in Livy, but we do not us= ing it to detect live/dead Livy instances. Each instance only reacts to the u= pdates to the ZooKeeper "session store", which is shared by all instances of= Livy. >=20 > Thanks, > Meisam >=20 >> On Wed, Jul 26, 2017 at 1:36 AM Vivek wrote: >> Ok.so if I start multiple instances how will I know which instance to sen= d the request to? >> And multiple instances would then be only controlled by the port id?=20 >>=20 >>=20 >> Sent from my iPhone >>=20 >>> On 26 Jul 2017, at 4:04 PM, Saisai Shao wrote: >>>=20 >>> Current Livy doesn't support the things you mentioned here. You can star= t multiple Livy in the cluster, but each LivyServer is a standalone service d= oesn't aware the existence of others. >>>=20 >>>> On Wed, Jul 26, 2017 at 10:27 AM, Vivek wrot= e: >>>> Hi, >>>>=20 >>>> We are now considering moving into a uat environment using Livy at my c= ompany. >>>>=20 >>>> Has anyone implemented multiple Livy instances on a single cluster with= load balancing? >>>>=20 >>>> A few questions. >>>> 1. Is this feature available in the 0.3 release? >>>> 2. How would I name/number the multiple instances I bring up? >>>> 3. How does one load balance and send requests across the multiple inst= ances? >>>> 4. Does Livy have a heartbeat mechanism to understand which or how many= instances are up? >>>>=20 >>>> Any answers would be appreciated. >>>>=20 >>>> Regards >>>> Vivek >>>>=20 >>>>=20 >>>> Sent from my iPhone >>>=20 --Apple-Mail-D807AF7D-E0D9-472B-AA34-D61F4AA7057D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thanks Meisam. 


Is this code in github? 
Is there a PR for this?
<= br>
Regards
Vivek


Sent from my iPhon= e

On 27 Jul 2017, at 12:51 AM, Meisam Fathi <meisam.fathi@gmail.com> wrote:

Hi Vivek,

<= div>We are running multiple instances of Livy on our clusters. Our users can= create and access jobs on any of the Livy instances.

To answer your particular question

1. Is= this feature available in the 0.3 release? No. The feature is not avail= able out of the box=E2=80=93we modified Livy to add this feature. 
2. How would I name/number the multiple instances I bring up? T= he load balancer knows all the instances. Users only interact with the load b= alancer.
3. How does one load balance and send requests across t= he multiple instances? Livy instances do not know that requests come fro= m a load balancer. Each processes requests it receives and updates a shared <= i>"session store", which we implemented on top of ZooKeeper.
<= b>4. Does Livy have a heartbeat mechanism to understand which or how many in= stances are up? No. There is a heartbeat mechanism in Livy, but we do no= t using it to detect live/dead Livy instances. Each instance only reacts to t= he updates to the ZooKeeper "session store", which is shared by a= ll instances of Livy.

Thanks,
Meisa= m

On Wed, Jul 26,= 2017 at 1:36 AM Vivek <vivek= suvarna@yahoo.co.in> wrote:
Ok.so if I start multiple instances how will I know whi= ch instance to send the request to?
And multiple instances would then be only controlled by th= e port id? 
<= br>

Sent from m= y iPhone

On 26 Jul 2017, at 4:04 PM, S= aisai Shao <s= ai.sai.shao@gmail.com> wrote:

=
Current Livy doesn't support the things you mentioned h= ere. You can start multiple Livy in the cluster, but each LivyServer is a st= andalone service doesn't aware the existence of others.

On Wed, Jul 26, 2017 at 10:27 AM,= Vivek <viveksuvarna@yahoo.co.in> wrote:
Hi,

We are now considering moving into a uat environment using Livy at my compan= y.

Has anyone implemented multiple Livy instances on a single cluster with load= balancing?

A few questions.
1. Is this feature available in the 0.3 release?
2. How would I name/number the multiple instances I bring up?
3. How does one load balance and send requests across the multiple instances= ?
4. Does Livy have a heartbeat mechanism to understand which or how many inst= ances are up?

Any answers would be appreciated.

Regards
Vivek


Sent from my iPhone

= --Apple-Mail-D807AF7D-E0D9-472B-AA34-D61F4AA7057D--