Description
Found out that ResourceCalculator.ratio (with implementors DefaultResourceCalculator and DominantResourceCalculator) can produce NaN (Not-A-Number) as a result.
This is because IEEE 754 defines 1.0 / 0.0 as Infinity and -1.0 / 0.0 as -Infinity and 0.0 / 0.0 as NaN, see here: https://stackoverflow.com/a/14138032/1106893
I think it's very dangerous to rely on NaN can be returned from ratio calculations and this could have side-effects.
When ratio calculates the result and if both the numerator and the denominator is zero, we should use 0 as a result, I think.
Attachments
Attachments
Issue Links
- is depended upon by
-
YARN-8059 Resource type is ignored when FS decide to preempt
- Open