Re: Rack awareness support for Mesos

.org <mailto:vinodk...@apache.org>> <mailto:vinodk...@apache.org <mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org <mailto:vinodk...@apache.org>>> <mailto:vinodk.

Re: Rack awareness support for Mesos

>> >> -- >> >> Aaron Carey >> Production Engineer - Cloud Pipeline >> Industrial Light & Magic >> London >> 020 375

Re: Rack awareness support for Mesos

emoortere; vinodk...@apache.org <mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org <mailto:vinodk...@apache.org>> <mailto:vinodk...@apache.org <mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org <

Re: Rack awareness support for Mesos

ttps://issues.apache.org/jira/browse/MESOS-3059 >> >> -- >> >> Aaron Carey >> Production Engineer - Cloud Pipeline >> Industrial Light & Magic >> London >> 020 3751 9150 &g

Re: Rack awareness support for Mesos

vinodk...@apache.org <mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org <mailto:vinodk...@apache.org>> Subject: Re: Rack awareness support for Mesos Hi everyone Let me summarize the discussion about Rack aw

Re: Rack awareness support for Mesos

lt;mailto:user@mesos.apache.org>; d...@mesos.apache.org <mailto:d...@mesos.apache.org> Cc: Joris Van Remoortere; vinodk...@apache.org <mailto:vinodk...@apache.org> Subject: Re: Rack awareness support for Mesos Hi everyone Let me summarize the discussion abo

Re: Rack awareness support for Mesos

t;> >> >> From: Du, Fan [fan...@intel.com <mailto:fan...@intel.com>] >> Sent: 14 June 2016 07:24 >> To: user@mesos.apache.org <mailto:user@mesos.apache.org>; >> d...@mesos.apache.org <mailto:d...@mesos

Re: Rack awareness support for Mesos

esos.apache.org <mailto:user@mesos.apache.org>; d...@mesos.apache.org <mailto:d...@mesos.apache.org> Cc: Joris Van Remoortere; vinodk...@apache.org <mailto:vinodk...@apache.org> Subject: Re: Rack awareness support for Mesos Hi everyone Let me summarize the di

Re: Rack awareness support for Mesos

time to > randomly shuffle the agents also grows. > > How about rearranging the agent in a per rack basis, and a minor change > to the way how resources are allocated will fix this. > > > I might not see the whole picture here, so comments are welcomed! > > > On 2016/6/

RE: Rack awareness support for Mesos

7:24 To: user@mesos.apache.org; d...@mesos.apache.org Cc: Joris Van Remoortere; vinodk...@apache.org Subject: Re: Rack awareness support for Mesos Hi everyone Let me summarize the discussion about Rack awareness in the community so far. First thanks for all the comments, advices or challenges! :)

Re: Rack awareness support for Mesos

folks I’ve been thinking about Mesos rack awareness support for a while, it’s a common interest for lots of data center applications to provide data locality, fault tolerance and better task placement. Create MESOS-5545 to track the story, and here is the initial design doc [1] to support rack

Re: Rack awareness support for Mesos

On 2016/6/8 0:58, james wrote: Do I have access to the jira system by default joining this list, or do I have to request permission somewhere? (sorry jira is new to me so recommendations on jira, per mesos, in a document, would be keen.) You need a JIRA account, sign up one here:

Re: Rack awareness support for Mesos

On Tuesday, June 7, 2016, Du, Fan wrote: > > > On 2016/6/6 23:48, Jörg Schad wrote: > >> Hi, >> thanks for your idea and design doc! >> Just a few thoughts: >> a) The scheduling part would be implemented in a framework scheduler and >> not the Mesos Core, or? >> > > I'm not

Re: Rack awareness support for Mesos

g in" resources, with a variety of parameters as a companion to > your idea, is warranted for these aforementioned use cases > and other opportunities. > > >> >>> Great idea. I do like it very much. >>> >>> hth, >>> James >>> &g

Re: Rack awareness support for Mesos

e, or not enable it? Cheers, On 06/06/16 10:17, Du, Fan wrote: Hi, Mesos folks I’ve been thinking about Mesos rack awareness support for a while, it’s a common interest for lots of data center applications to provide data locality, fault tolerance and better task placement. Create MES

RE: Rack awareness support for Mesos

: Du, Fan [fan...@intel.com] Sent: 07 June 2016 16:16 To: Jörg Schad; user@mesos.apache.org Subject: Re: Rack awareness support for Mesos On 2016/6/6 23:48, Jörg Schad wrote: > Hi, > thanks for your idea and design doc! > Just a few thoughts: > a) The scheduling part would be implemente

Re: Rack awareness support for Mesos

ers, On 06/06/16 10:17, Du, Fan wrote: Hi, Mesos folks I’ve been thinking about Mesos rack awareness support for a while, it’s a common interest for lots of data center applications to provide data locality,

Re: Rack awareness support for Mesos

folks I’ve been thinking about Mesos rack awareness support for a while, it’s a common interest for lots of data center applications to provide data locality, fault tolerance and better task placement. Create MESOS-5545 to track the story, and here is the initial design doc [1] to support rack awa

Re: Rack awareness support for Mesos

> >> This looks potentially interesting. How does it work in a public cloud >> deployment scenario? I assume you would just have to disable this >> feature, or not enable it? >> >> Cheers, >> >> On 06/06/16 10:17, Du, Fan wrote: >> >>> H

Re: Rack awareness support for Mesos

Gran wrote: Hi, This looks potentially interesting. How does it work in a public cloud deployment scenario? I assume you would just have to disable this feature, or not enable it? Cheers, On 06/06/16 10:17, Du, Fan wrote: Hi, Mesos folks I’ve been thinking about Mesos rack awareness support

Re: Rack awareness support for Mesos

Hi, This looks potentially interesting. How does it work in a public cloud deployment scenario? I assume you would just have to disable this feature, or not enable it? Cheers, On 06/06/16 10:17, Du, Fan wrote: > Hi, Mesos folks > > I’ve been thinking about Mesos rack awarenes

Rack awareness support for Mesos

Hi, Mesos folks I've been thinking about Mesos rack awareness support for a while, it's a common interest for lots of data center applications to provide data locality, fault tolerance and better task placement. Create MESOS-5545 to track the story, and here is the initial design doc [1