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

Hudson commented on YARN-3835:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #226 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/226/])
YARN-3835. hadoop-yarn-server-resourcemanager test package bundles 
core-site.xml, yarn-site.xml (vamsee via rkanter) (rkanter: rev 
99271b762129d78c86f3c9733a24c77962b0b3f7)
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/pom.xml


> hadoop-yarn-server-resourcemanager test package bundles core-site.xml, 
> yarn-site.xml
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-3835
>                 URL: https://issues.apache.org/jira/browse/YARN-3835
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Vamsee Yarlagadda
>            Assignee: Vamsee Yarlagadda
>            Priority: Minor
>             Fix For: 2.8.0
>
>         Attachments: YARN-3835.patch
>
>
> It looks like by default yarn is bundling core-site.xml, yarn-site.xml in 
> test artifact of hadoop-yarn-server-resourcemanager which means that any 
> downstream project which uses this a dependency can have a problem in picking 
> up the user supplied/environment supplied core-site.xml, yarn-site.xml
> So we should ideally exclude these .xml files from being bundled into the 
> test-jar. (Similar to YARN-1748)
> I also proactively looked at other YARN modules where this might be 
> happening. 
> {code}
> vamsee-MBP:hadoop-yarn-project vamsee$ find . -name "*-site.xml"
> ./hadoop-yarn/conf/yarn-site.xml
> ./hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/test/resources/yarn-site.xml
> ./hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/resources/yarn-site.xml
> ./hadoop-yarn/hadoop-yarn-client/src/test/resources/core-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/core-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/core-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/yarn-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/target/test-classes/core-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/target/test-classes/yarn-site.xml
> ./hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/resources/core-site.xml
> {code}
> And out of these only two modules (hadoop-yarn-server-resourcemanager, 
> hadoop-yarn-server-tests) are building test-jars. In future, if we start 
> building test-jar of other modules, we should exclude these xml files from 
> being bundled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to