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

Hudson commented on YARN-7358:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13139 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13139/])
YARN-7358. TestZKConfigurationStore and TestLeveldbConfigurationStore (rkanter: 
rev 2da654e34a436aae266c1fbdec5c1067da8d854e)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/conf/ConfigurationStoreBaseTest.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/conf/TestLeveldbConfigurationStore.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/conf/TestZKConfigurationStore.java


> TestZKConfigurationStore and TestLeveldbConfigurationStore should explicitly 
> set capacity scheduler
> ---------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7358
>                 URL: https://issues.apache.org/jira/browse/YARN-7358
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>            Priority: Minor
>             Fix For: 2.9.0, 3.0.0
>
>         Attachments: YARN-7358.00.patch, YARN-7358.01.patch
>
>
> TestZKConfigurationStore and TestLeveldbConfigurationStore both assume 
> capacity scheduler in RM. They should set it explicitly in configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to