Re: Can tasks from multiple frameworks simultaneously run on the same slave node?

Hi Daniel, this depends on your framework: Mesos assumes that a framework is "well behaved", i.e. only requests the resources that it really needs. A framework can control this using SchedulerDriver::requestResources() call. Therefore a framework might not take all available resources of an

Re: Can tasks from multiple frameworks simultaneously run on the same slave node?

re (a): Yes, it's current behavior; but MESOS-3765 is to enhance it. re (b): partly: 0. I'm not sure I understand your point on "actually used to launch tasks", but my point is that Mesos did not know whether "task" is right; Mesos depedent on

Weird Error on One Node

I am trying to start a task on a node, and it keeps failing with no logs in the sandbox (it's blank) In the slave logs, I get the error below. I looked into MESOS-3352 and since I am running RHEL 7 with Version 208 (that "should" be the patched version based on what I've read). I am thinking

Re: Weird Error on One Node

I tried restarting the slave again and this time it worked... *shrug* That said, anything I can do next time this happens? Do I need to do something on RHEL7 and Cgroups to make the info in MESOS-3352 work? Thanks! John On Fri, Dec 4, 2015 at 1:54 PM, John Omernik wrote: >

Re: mesos ui best practise - mesos cluster in HA

Jeremy, This works for me!! Thanks a lot! All, Thanks for suggesting the possible ways I can do it. On Wed, Dec 2, 2015 at 6:50 PM, Jeremy Olexa wrote: > This is what we use in haproxy: > > backend master_cluster > option httpclose > option forwardfor > mode

Re: Can tasks from multiple frameworks simultaneously run on the same slave node?

Just want to show more detail for offer_timeout, currently, there is no default value for it, you may want to specify a value such as "5s" when start up mesos master. Then if the offer was not handled in 5s, it will be returned to master automatically. Cited from