Andrew Schwartzmeyer commented on MESOS-8631:

I believe this should be back-ported to Mesos 1.5.1.

> Can't start a task with every CPU on a Windows machine
> ------------------------------------------------------
>                 Key: MESOS-8631
>                 URL: https://issues.apache.org/jira/browse/MESOS-8631
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>         Environment: Windows 10 using the CPU isolator
>            Reporter: Andrew Schwartzmeyer
>            Assignee: Andrew Schwartzmeyer
>            Priority: Critical
>              Labels: cpu, isolator, windows
>             Fix For: 1.5.1
> We have an edge case that existing unit tests don't cover: starting a single 
> task which consumes every reported CPU. The problem is that the executor 
> overcommits by 0.1 CPUs, so when we go to set the CPU limit, on say a 12 core 
> machine, we set it to 12.1/12 * 10000 CPU cycles, which results in an invalid 
> number of cycles (10,083, but the max is 10,000).
> We were bounds-checking the minimum (1 cycle) but not the maximum, as the 
> function did not expect the user to request more CPUs than available.
> We'll fix this by checking the max bound. So if, for example, 12.1 CPUs are 
> requested, re set the limit to 10000 CPU cycles, no more.

This message was sent by Atlassian JIRA

Reply via email to