[
https://issues.apache.org/jira/browse/MESOS-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097027#comment-15097027
]
Neil Conway commented on MESOS-3341:
------------------------------------
[~jessicahartog] -- As part of MESOS-3997, we're planning on only supporting
three decimal digits of precision (e.g., 1.001 CPUs) for scalar resource values.
An open question is what we should do if the user tries to, say, reserve
1.00001 CPUs (using the old floating point input format). Should such a request
be rounded to three decimal digits of precision? Perhaps rounded with a
warning? Should it be rejected with an error?
> 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)
