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

Hadoop QA commented on AMBARI-20400:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12857722/AMBARI-20400.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11007//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11007//console

This message is automatically generated.

> Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not 
> installed on the cluster
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20400
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20400
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: trunk
>
>         Attachments: AMBARI-20400.patch
>
>
> It's possible to install a cluster without Tez and Slider via blueprint. In 
> this case, Yarn historyserver start logic prints two warnings about unable to 
> copy tez and slider tar ball to HDFS.
> Yarn history server should skip the copy hdfs tar ball logic for tez and 
> slider if they are not installed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to