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

Hadoop QA commented on AMBARI-21696:
------------------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11969//console

This message is automatically generated.

> Spark thrift service was alerting for connectivity for all newly created 
> clusters
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-21696
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21696
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Mingjie Tang
>            Assignee: Mingjie Tang
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21696.patch
>
>
> Error: Could not open client transport with JDBC Uri: 
> jdbc:hive2://hn0-salqa0.lv5aupozrfhezhozcxr3xjcwqe.dx.internal.cloudapp.net:10016/default:
>  java.net.ConnectException: Connection refused (Connection refused) 
> (state=08S01,code=0)
> This is belong to the alert service does not change the port number based on 
> model. 



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

Reply via email to