Ben, Thanks for the reply. So my understanding is if some isolation module (in this case cgroups) needs certain resource values to be specified, I would need to specify those even if I am using a different isolation module, is that right? I am a bit worried that future releases might require other resource values to be specified that would break my framework.
Li On Thu, Aug 29, 2013 at 3:10 PM, Benjamin Hindman < [email protected]> wrote: > When we attempt to isolate the resources via control groups on Linux we > need at least some value. That being said, isolation is coarser grained > than what you can specify with a double, and 0.0001 gets rounded to a > different value (via cpu shares). I could imagine doing validation on cpu > resources to not allow something below the granularity that we can actually > isolate. How does that sound? > > > On Thu, Aug 29, 2013 at 8:58 AM, Li Jin <[email protected]> wrote: > >> Hello guys, >> >> I have observed this behavior: >> >> (1) If I launchTasks with a task with no resource spec, mesos says "Error >> validating task 6901953 : Task uses no resources" >> (2) If I launchTasks with a task with cpu=0.00001 and no other resource >> spec, mesos launches the task >> >> These two seem to be practically the same, I am wondering what's the >> rationale to have different behavior for these two cases. >> >> Thanks, >> Li >> > >
