Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CACeBwqxEjgK5rDQZvUiYLU-SYrMK9XrxogWWZObUGew1p+BOYQ@mail.gmail.com>
References: 
 <CANrnGxfJRkL+boDtzJUz5SKiDt4tDPZam-pc-9bBXM9jpWQ3sQ@mail.gmail.com>
	<CANrnGxfKBEzQa+2Hc5dYTCkeHFMPsektjCWcMyhNFs=TJ1TaKw@mail.gmail.com>
	<3D60EFBB-BE04-4236-8275-149FA16391E9@gmail.com>
	<CACeBwqxakXWYjtHtb83ibQcoeLVpMwico4EMSmcSLHu3VuER=g@mail.gmail.com>
	<CANrnGxcfEa5s3hPrx6RkGfhTVYbKgwMq9FJyAFuuMR3AKGMjxw@mail.gmail.com>
	<CACzFoUsijpdx1hS27E-TT0+UYf8B4shX-d9_A=v6gUP3V+Vhiw@mail.gmail.com>
	<CANrnGxfEzmnih6myguYU+JWHPxYNhwhvfMwAF2aOTuK+gXXLUA@mail.gmail.com>
	<CACeBwqxEjgK5rDQZvUiYLU-SYrMK9XrxogWWZObUGew1p+BOYQ@mail.gmail.com>
Date: Mon, 28 Dec 2015 23:51:58 +0100
Message-ID: 
 <CACzFoUur6SVqJ-CjiQRgZmcx8G7BcOBbTiVFL63sVCXMm1VDiQ@mail.gmail.com>
Subject: Re: mesos-elasticsearch vs Elasticsearch with Marathon
From: Alex Rukletsov <alex@mesosphere.com>
To: user@mesos.apache.org
Cc: Frank Scholten <frank.scholten@container-solutions.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Craig,

mind elaborating, how exactly do you run elasticsearch in Marathon?

On Mon, Dec 28, 2015 at 8:36 PM, craig w <codecraig@gmail.com> wrote:
> In terms of discovery, elasticsearch provides that out of the box
> https://www.elastic.co/guide/en/elasticsearch/reference/1.4/modules-disco=
very.html.
> We deploy elasticsearch via Marathon and it works great.
>
> On Mon, Dec 28, 2015 at 2:17 PM, Eric LEMOINE <elemoine@mirantis.com> wro=
te:
>>
>> On Mon, Dec 28, 2015 at 7:55 PM, Alex Rukletsov <alex@mesosphere.com>
>> wrote:
>> > Eric=E2=80=94
>> >
>> > give me a chance to answer that before you fall into frustration : ).
>> > Also, you can directly write to framework developers
>> > (mesos-es@container-solutions.com) and they either confirm or bust my
>> > guess. Or maybe one of the authors =E2=80=94 Frank =E2=80=94 will chim=
e in in this
>> > thread.
>> >
>> > Marathon has no idea about application logic, hence a "scale"
>> > operation just starts more application instances. But sometimes you
>> > may want to do extra job (track instances, report ip:port of a new
>> > instance to existing instances, and so on). That's when a dedicated
>> > framework makes sense. Each framework has a scheduler that is able to
>> > track each instance and do all aforementioned actions.
>> >
>> > How this maps to your question? AFAIK, all Elasticsearch nodes should
>> > see each other, hence once a new node is started, it should be somehow
>> > advertised to other nodes. You can do it by wrapping Elasticsearch
>> > command in a shell script and maintain some sort of an out-of-band
>> > registry, take a look at one of the first efforts [1] to run
>> > Elasticsearch on Mesos to get an impression how it may look like. But
>> > you can use a dedicated framework instead : ).
>> >
>> > [1] https://github.com/mesosphere/elasticsearch-mesos
>>
>>
>> That makes great sense Alex. Thanks for chiming in.
>
>
>
>
> --
>
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
> https://twitter.com/mind_scratch
> https://twitter.com/craig_links