Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
As allocations are stored/transmitted as doubles many a times precision errors creep in.
we have seen erroneous share calculations happen only because of floating point arithmetic.
Attachments
Issue Links
- is related to
-
MESOS-3997 Switch to fixed-point for resources
- Accepted
-
MESOS-3552 CHECK failure due to floating point precision on reservation request
- Resolved
- relates to
-
MESOS-3090 Calculated CPU should be rounded
- Resolved
-
MESOS-4071 Master crash during framework teardown (Check failed: total.resources.contains(slaveId))
- Resolved