[
https://issues.apache.org/jira/browse/MESOS-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097574#comment-15097574
]
Erik Weathers commented on MESOS-3341:
--------------------------------------
[~neilc]: seems unlikely that anyone is carving up CPUs at such a granularity.
So the question of how to handle this "resource resolution" comes down to what
the best behavior to exhibit in the rare case that it *does* happen. My
perspective is that we should go with the least surprising behavior, and
changing the requested resources in-transit seems to run counter to that
principle.
> Introduce Resource Resolution
> -----------------------------
>
> Key: MESOS-3341
> URL: https://issues.apache.org/jira/browse/MESOS-3341
> Project: Mesos
> Issue Type: Improvement
> Reporter: Jessica Hartog
> Priority: Minor
>
> After MESOS-1807, Mesos containers require >= 0.01 CPU resources and >= 32MB
> Memory resources. In order to simplify accounting, Mesos should introduce
> resource resolution.
> For example, it is possible to launch a task with 1.0000000000001 CPU (as it
> exceeds the minimum number of CPUs and is therefore considered valid). The
> fractional component of this task does not benefit the running process, and
> can introduce floating point errors when Mesos is accounting its offers
> (which we have already seen happening in MESOS-1867 and MESOS-2635). A
> solution to this could be disallowing tasks with finer granularity than the
> required resolution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
