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 Thu, 19 Nov 2015 15:58:10 GMT

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

Jason Lowe commented on YARN-4374:

I don't know the full history behind why %.1f was used, but I think it may be to help hide
single-precision floating point precision problems.  For example:
$ python -c "print repr(0.1)"

So we may still want to have some reasonable limit on the precision we will attempt to show
on the UI to hide the annoying effects like the example above.  It looks like %.1f is hiding
too much.  Maybe %.3f is more reasonable?  We're already treating other percentages rendered
in the UI effectively as %.3f once we account for the scale by 100.

> 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.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