You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2015/11/25 20:50:11 UTC
[jira] [Updated] (MESOS-3990) Unexpected reservation results due to
floating point error
[ https://issues.apache.org/jira/browse/MESOS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Conway updated MESOS-3990:
-------------------------------
Labels: mesosphere reservations tech-debt (was: )
Priority: Major (was: Critical)
Component/s: master
Summary: Unexpected reservation results due to floating point error (was: Doubles Don't Work for Resource Reservation)
On reflection, reopening because this is a distinct issue: MESOS-3552 and MESOS-1187 are about a crashing bug, whereas this talks about unexpected user-visible behavior.
In the short-term, the workaround is for frameworks to compare reserved resources within an epsilon. Long-term fix is to switch to a fixed-point representation (MESOS-3997).
> Unexpected reservation results due to floating point error
> ----------------------------------------------------------
>
> Key: MESOS-3990
> URL: https://issues.apache.org/jira/browse/MESOS-3990
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Gabriel Hartmann
> Labels: mesosphere, reservations, tech-debt
>
> When issuing a RESERVE operation requesting the below, I received a reservation with the wrong value (6566.4002):
> resources {
> name: "mem"
> type: SCALAR
> scalar {
> value: 6566.4001
> }
> role: "role1"
> reservation {
> principal: "default-principal"
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)