mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Mathiske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3552) CHECK failure due to floating point precision on reservation request
Date Thu, 26 Nov 2015 14:32:11 GMT

    [ https://issues.apache.org/jira/browse/MESOS-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028894#comment-15028894
] 

Bernd Mathiske commented on MESOS-3552:
---------------------------------------

As mentioned above, this does not solve the general problem, for which there is more to come
in this epic.

> CHECK failure due to floating point precision on reservation request
> --------------------------------------------------------------------
>
>                 Key: MESOS-3552
>                 URL: https://issues.apache.org/jira/browse/MESOS-3552
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Mandeep Chadha
>            Assignee: Mandeep Chadha
>              Labels: mesosphere, tech-debt
>
> result.cpus() == cpus() check is failing due to ( double == double ) comparison problem.

> Root Cause : 
> Framework requested 0.1 cpu reservation for the first task. So far so good. Next Reserve
operation — lead to double operations resulting in following double values :
>  results.cpus() : 23.9999999999999964472863211995 cpus() : 24
> And the check ( result.cpus() == cpus() ) failed. 
>  The double arithmetic operations caused results.cpus() value to be :  23.9999999999999964472863211995
and hence ( 23.9999999999999964472863211995 == 24 ) failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message