Re: A question about "left over" rejected resources

Got it. Thanks! On Mon, Apr 6, 2015 at 9:02 PM, Vinod Kone wrote: > To clarify David's answer, you should only get <16, 8> offer until the > filter on <0, 8> is active. Once the filter expires (or you call > reviveOffers), Mesos will consolidate those resources and send a <16, 16> > offer. You d

Re: hadoop client on mesos

Mesos does not come with an HDFS client built-in. You have a couple of options: 1) Use the new HDFS framework (not yet tested in production) 2) Install HDFS (not necessarily the full Hadoop) on your cluster manually, make sure the client is installed on each sl

hadoop client on mesos

What do I need to put on the mesos master and slaves, to let access them hdfs where the packages are stored ? Is there already an hdfs client on mesos ? When I install hadoop-client from cloudera repos, it is installing me zookeeper, ... and so on, and after that my master is no longer working pro

Re: A question about "left over" rejected resources

To clarify David's answer, you should only get <16, 8> offer until the filter on <0, 8> is active. Once the filter expires (or you call reviveOffers), Mesos will consolidate those resources and send a <16, 16> offer. You don't need to restart the master for the aggregation. On Mon, Apr 6, 2015 at

Re: Custom python executor with Docker

Tim, do you want answer this? On Wed, Apr 1, 2015 at 7:27 AM, Tom Fordon wrote: > Hi. I'm trying to understand using docker within a custom executor. For > each of my tasks, I would like to perform some steps on the node before > launching a docker container. I was planning on writing a custom

Re: A question about "left over" rejected resources

Thanks David! I'd like to make sure I understand you correctly. I will get both <16,8> & <0,8> offers, or just the <16,8> offer? (because I previously rejected the <0,8> offer, and did not call reviveOffers) On Mon, Apr 6, 2015 at 3:06 PM, David Greenberg wrote: > You'll actually see that as 2

Re: A question about "left over" rejected resources

You'll actually see that as 2 offers: <16,8> and <0,8>. Your framework may need to consolidate those offers if it requires more than 8gb of memory for the next task; you can do that by calling launchTasks with both offers. Besides combining offers in the framework, if you fail over the master, the

A question about "left over" rejected resources

Say my scheduler received a resource offers from slave S with <16cpu, 16GiB mem>, and called launchTasks on this offer with utilization of <16cpu, 8GiB mem>. >From what I see (with mesos 0.21), the left over <0cpu, 8GiB mem> is considered rejected, and will be re-offered after the rejection filter,