Re: Framework taking default resources even though a role is specified

> mesos-execute support constraints Currently don't support. On Sat, Apr 16, 2016 at 11:17 PM, June Taylor wrote: > Thank you for that suggestion, it seems to be exactly what we're looking > to do. Does mesos-execute support constraints? > > > Thanks, > June Taylor > System Administrator, Minnes

Re: Framework taking default resources even though a role is specified

Thank you for that suggestion, it seems to be exactly what we're looking to do. Does mesos-execute support constraints? Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Sat, Apr 16, 2016 at 9:57 AM, haosdent wrote: > >We expect these tasks to onl

Re: Framework taking default resources even though a role is specified

>We expect these tasks to only go on nodes with the "production" resource role. Actually most frameworks support constraints(spark/marathon/chronos). It could be used to limit tasks executed on the Mesos Agent that satisfied conditions. For your scenario, you could restart Mesos agent by adding `-

Re: Framework taking default resources even though a role is specified

Which version are you using? For your requirement, I think you can try Quota; currently, the resources beyond quota will not offer to the framework whose quota satisfied. Quota will also include reserved resources. Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Te

Re: Framework taking default resources even though a role is specified

You can try setting constraints on tasks in both Chronos and marathon that will limit deployment to only a certain set of nodes.  Sent from Outlook for iPhone On Fri, Apr 15, 2016 at 1:35 PM -0700, "June Taylor" wrote: Evan, I'm not sure about it. We're new to the Mesos system and

Re: Framework taking default resources even though a role is specified

Evan, I'm not sure about it. We're new to the Mesos system and still learning. We want to be able to classify resources so that our developers can run tasks against them easily, without using more than they are permitted. It seemed like resource roles were the appropriate solution, but they may no

Re: Framework taking default resources even though a role is specified

My understanding is that your framework would have to know not to accept offers for * resources. Marathon has an option to specify which roles to accept for a particular app, and has command line options for controlling the default. Maybe pyspark has something similar? On Fri, Apr 15, 2016 at 1:24

Re: Framework taking default resources even though a role is specified

Yep - we're waiting for it. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Fri, Apr 15, 2016 at 3:23 PM, Anand Mazumdar wrote: > FWIW, we recently fixed `mesos-execute` (command scheduler) to add support > for roles. It should be available in t

Re: Framework taking default resources even though a role is specified

FWIW, we recently fixed `mesos-execute` (command scheduler) to add support for roles. It should be available in the next release (0.29). https://issues.apache.org/jira/browse/MESOS-4744 -anand > On Apr 15, 2016, at 11:41 AM, June Taylor wrote

Re: Framework taking default resources even though a role is specified

Ken, Thanks for your reply. Is there a way to ensure a framework only receives the reserved resources? I would go ahead and take everything out of the * role, however, the 'mesos-execute' command doesn't support specifying a role, so that's the only way we can currently get mesos-execute to co-e

Re: Framework taking default resources even though a role is specified

The framework with role “production” will receive production resources and * resources All other frameworks (assuming no role) will only receive * resources ken > On Apr 15, 2016, at 11:38 AM, June Taylor wrote: > > We have a small cluster with 3 nodes in the * resource role default, and 3 >

Framework taking default resources even though a role is specified

We have a small cluster with 3 nodes in the * resource role default, and 3 nodes in a "production" resource role. Starting up a framework which requests "production" properly executes on the expected nodes, however, today we noticed that this job also started up executors under the * resource role