>From Mesos point of view, a resource is just a string, your agents may
advertise "gpu", "bananas", "pandas" and so on. However, some resources are
known to Mesos, and for them isolation is possible. A good example is a
cgroups isolator for "mem" resources, which will invoke OOM killer if
necessary. Compare with GPU resources: if your agent advertises, say, 1GB
"gpu" to the master, a task may accept 100MB, but the agent will have no
control, whether a task uses no more than 100MB, because there is no
isolator for this resource. Good news is that you can write an isolator for
your resource, wrap it into a Mesos module, and let Mesos agent use it!
P.S. "cpu" is not a known resource, but "cpus" is.
On Tue, Aug 25, 2015 at 7:31 PM, craig w wrote:
> When configuring a mesos-slave with "--resources", I know "cpu", "mem" and
> "ports" are available. Are there others? Are these documented somewhere?
>
> I've found some examples here
> https://open.mesosphere.com/reference/mesos-slave/ and the configuration
> page (http://mesos.apache.org/documentation/latest/configuration/) is
> generic with it's description of "--resources".
>
> Thanks
> craig
>
