hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4374) RM scheduler UI rounds user limit factor
Date Fri, 20 Nov 2015 15:08:11 GMT

    [ https://issues.apache.org/jira/browse/YARN-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018131#comment-15018131

Jason Lowe commented on YARN-4374:

On second thought, I think the first approach is more appropriate.  Float formatting is already
truncating to 6 digits of precision after the decimal point (and discarding unnecessary zeroes).
 Since this is a case where we are not applying any kind of calculation to the value parsed
from the config then I think we can just rely on the standard float formatting to convey the
value we parsed.  If we were calculating the user limit then we could definitely run into
precision annoyances like 0.250001 instead of 0.25, but since we're not calculating we shouldn't
hit them.

So +1 for the original patch.  Will commit later today if there are no objections.

> RM scheduler UI rounds user limit factor
> ----------------------------------------
>                 Key: YARN-4374
>                 URL: https://issues.apache.org/jira/browse/YARN-4374
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: Screenshot1.png, YARN-4374.2.patch, YARN-4374.patch
> RM scheduler UI rounds user limit factor, such as from  0.25 up to 0.3

This message was sent by Atlassian JIRA

View raw message