Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 412EB10938 for ; Mon, 14 Oct 2013 19:03:48 +0000 (UTC) Received: (qmail 2202 invoked by uid 500); 14 Oct 2013 19:03:47 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 1775 invoked by uid 500); 14 Oct 2013 19:03:42 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 898 invoked by uid 99); 14 Oct 2013 19:03:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 19:03:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of flo@mesosphe.re designates 209.85.223.171 as permitted sender) Received: from [209.85.223.171] (HELO mail-ie0-f171.google.com) (209.85.223.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 19:03:36 +0000 Received: by mail-ie0-f171.google.com with SMTP id at1so15199169iec.2 for ; Mon, 14 Oct 2013 12:03:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mesosphe.re; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Dfh0pn7vWMw2Ko21T11b7lhQuNo7Z5x6Ao4QHkAc7qs=; b=eHrthK8lBAn7S2KUvFou53pMHfQnAbULa6vIOx6GvNL4Wkb4XBHu4Fq/CFgDsw6K5y Osmfz+4iLvy82dI/SOgen/JYNxV0ubfaIJSe2nHseDAcjYywckWp9jWfzmmKOFBgZbW3 Pjj8gW22cr6h6hp/9N/lw+N+WfV6FTsAFlM4g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Dfh0pn7vWMw2Ko21T11b7lhQuNo7Z5x6Ao4QHkAc7qs=; b=HhvkLMEhZNQIvf1HcJKEVGXGxuucQeqwPD6D4fr/kN5kgrggBhcZUKdQKPUPC9WeK8 C/XG71JqCaY4XkEepSdha9Z9ipM6uM201QuOWygeTCJ+owDE4gOL9SMnxhFoYV9oFYf/ WHokR8rw1wCSYBGvAy5ZDAhEvUcXMZVoWWlMC4HKL6hJlPmYusHMMQI/L3NLewntOlpO qRnVZVQpkpiprBcGj29pQeaEDztR3ijttcJaAt2nvpiI4rNY5F0whlWU/e08FYKTXfEo NogXmdXV7fmewvQeqC2HnlTppEp5QYO9ptJi9Kvkmw6QTxwSuo5irHHdaf9h596k5txi Qfrg== X-Gm-Message-State: ALoCoQknncW0QXNy3cSi/zfLc8RWNj2zU5PlzUEtkcXd12Nd2i4iVEvkMIftSv1fx5CIH7D5HmSL MIME-Version: 1.0 X-Received: by 10.50.55.40 with SMTP id o8mr14428117igp.25.1381777395361; Mon, 14 Oct 2013 12:03:15 -0700 (PDT) Received: by 10.64.70.136 with HTTP; Mon, 14 Oct 2013 12:03:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 14 Oct 2013 12:03:15 -0700 Message-ID: Subject: Re: It is make sense to use memo to manage Ruby/Sinatra app? From: Florian Leibert To: "user@mesos.apache.org" , Ryan Chan Content-Type: multipart/alternative; boundary=047d7b10caa9cf84ba04e8b81e41 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10caa9cf84ba04e8b81e41 Content-Type: text/plain; charset=ISO-8859-1 Hi Ryan I think you might be interested in looking at Marathon. Marathon allows you to keep n instances of an application running in a cluster and will ensure that if one of them dies, another one takes over. It also aims to solve service discovery along the way. If you're familiar with Play! which is the "rails of the JVM", you could take a look at this tutorial which explains all the steps in detail: http://typesafe.com/blog/play-framework-grid-deployment-with-mesos. The only difference would be that you start your ruby app instead of the play application. Let me know if you have any more questions. --Flo On Sun, Oct 13, 2013 at 9:26 PM, Ryan Chan wrote: > Hello, > > We have a lot of Ruby/Sinatra apps written in house for different > purposes. > > As you know that Ruby limitation on threading so currently we launch a lot > of ruby process in a single machine (with different ports) in order to > utilize the CPU power. They are behind a AWS ELB for load balancing. > > To manage these ruby process is quite manual as some app use more > resource, while some app use less resource, so we cannot deploy too many > ruby process on a single machine to prevent overload, the drawback is some > resources are wasted. > > I heard people use meso to manage Java app such as Spark, I am thinking if > it make sense to integrate memo with my ruby app, anyone tried this before? > > > > > --047d7b10caa9cf84ba04e8b81e41 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Ryan=A0

I think you might be interested in looking at Marathon.= Marathon allows you to keep n instances of an application running in a clu= ster and will ensure that if one of them dies, another one takes over. It a= lso aims to solve service discovery along the way.

If you'= re familiar with Play! which is the "rails of the JVM", you could= take a look at this tutorial which explains all the steps in detail: h= ttp://typesafe.com/blog/play-framework-grid-deployment-with-mesos. The = only difference would be that you start your ruby app instead of the play a= pplication.

Let me know= if you have any more questions.

=
--Flo

On Sun, = Oct 13, 2013 at 9:26 PM, Ryan Chan <ryanchan404@gmail.com> wrote:
Hello,

We have a lot o= f=A0=A0Ruby/Sinatra apps written in house for different purposes.=A0

As you know that Ruby limitation on threading so curren= tly we launch a lot of ruby process in a single machine (with different por= ts) in order to utilize the CPU power. They are behind a AWS ELB for load b= alancing.

To manage these ruby process is quite manual as some ap= p use more resource, while some app use less resource, so we cannot deploy = too many ruby process on a single machine to prevent overload, the drawback= is some resources are wasted.

I heard people use meso to manage Java app such as Spar= k, I am thinking if it make sense to integrate memo with my ruby app, anyon= e tried this before?





--047d7b10caa9cf84ba04e8b81e41--