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

Hudson commented on YARN-7789:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13654 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13654/])
YARN-7789. Should fail RM if 3rd resource type is configured but RM uses 
(wangda: rev 042ef2fa7bcc22e3ca4eb8205c34d83e594bc7de)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacitySchedulerWithMultiResourceTypes.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java


> Should fail RM if 3rd resource type is configured but RM uses 
> DefaultResourceCalculator
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-7789
>                 URL: https://issues.apache.org/jira/browse/YARN-7789
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Sumana Sathish
>            Assignee: Zian Chen
>            Priority: Critical
>             Fix For: 3.1.0
>
>         Attachments: YARN-7789.001.patch, YARN-7789.002.patch
>
>
> We may need to revisit this behavior: Currently, RM doesn't fail if 3rd 
> resource type is configured, allocated containers will be automatically 
> assigned minimum allocation for all resource types except memory, this makes 
> really hard for troubleshooting. I prefer to fail RM if 3rd or more resource 
> type is configured inside resource-types.xml. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to