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

Hudson commented on YARN-7291:
------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17160 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17160/])
YARN-7291. Better input parsing for resource in allocation file. (snemeth: rev 
7ab88dbfa6fceaf8fea80eff1b23ed1ac486b393)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairSchedulerConfiguration.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairSchedulerConfiguration.java


> Better input parsing for resource in allocation file
> ----------------------------------------------------
>
>                 Key: YARN-7291
>                 URL: https://issues.apache.org/jira/browse/YARN-7291
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>    Affects Versions: 3.1.0
>            Reporter: Yufei Gu
>            Assignee: Zoltan Siegl
>            Priority: Minor
>              Labels: newbie
>             Fix For: 3.3.0
>
>         Attachments: YARN-7291.001.patch, YARN-7291.002.patch, 
> YARN-7291.003.patch, YARN-7291.004.patch, YARN-7291.005.patch, 
> YARN-7291.005.patch
>
>
> When you set max/min share for queues in fair scheduler allocation file,  
> "1024 mb, 2 4 vcores" is parsed the same as "1024 mb, 4 vcores" without any 
> issue, the same to "50% memory, 50% 100%cpu" which is parsed the same as "50% 
> memory, 100%cpu". That causes confusing. We should fix it. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to