I'm in the process of rewriting our framework to take account of roles in
mesos but am having trouble understanding the intended behaviour of roles.

If I have a slave started with --resources='cpus:4;cpus(role1):2' and a
framework registered with a role of 'role1', the framework start receiving
the role1 offer of 2 cpus as expected, but when I launch tasks for that
offer using up all cpus, the framework starts receiving an offer of role
'*' with 4 cpus while the 'role1' offers are busy / not available.

Is this the intended behaviour?

Is there any documentation on the behaviour of roles, weights, and how they
are intended to be used/implemented?


Radek

Reply via email to