[
https://issues.apache.org/jira/browse/AMBARI-20333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927171#comment-15927171
]
Hudson commented on AMBARI-20333:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7050 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7050/])
AMBARI-20333 - Value for User Limit Factor should be float instead of
(sangeetar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=df4c44a04dece13565927f34e14766876826accf])
* (edit)
contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js
* (edit)
contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/queue.hbs
> Value for "User Limit Factor" should be float instead of integer in YARN
> Queue Manager.
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-20333
> URL: https://issues.apache.org/jira/browse/AMBARI-20333
> Project: Ambari
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Anita Gnanamalar Jebaraj
> Assignee: Anita Gnanamalar Jebaraj
> Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20333.patch, screenshot-1.png
>
>
> According to yarn documentation,
> "yarn.scheduler.capacity.<queue-path>.user-limit-factor" should be a float:
> https://hadoop.apache.org/docs/r2.4.1/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
> Hence the user should be allowed to enter decimal values for 'User limit
> factor'
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
