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 <[email protected]> wrote: > 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 <[email protected]> wrote: > > 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-exist with pyspark. > > Any other thoughts from the group? > > > Thanks, > June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Fri, Apr 15, 2016 at 11:54 AM, Ken Sipe <[email protected]> wrote: > >> 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 <[email protected]> wrote: >> > >> > 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 as well. >> > >> > We expect these tasks to only go on nodes with the "production" >> resource role. Can you advise further? >> > >> > Thanks, >> > June Taylor >> > System Administrator, Minnesota Population Center >> > University of Minnesota >> >> > >
