ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18033) Hive2/HiveServer2 alert doesn't get the correct port to check the status.
Date Fri, 05 Aug 2016 19:33:20 GMT

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

Hudson commented on AMBARI-18033:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5466 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5466/])
AMBARI-18033. Hive2/HiveServer2 alert doesn't get the correct port to (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e11aa3b9bdf00ffc344e72371d3ab8897cd377f3])
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_interactive_thrift_port.py


> Hive2/HiveServer2 alert doesn't get the correct port to check the status.
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18033
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18033
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18033.patch
>
>
> - Seen in Wire encrypted cluster.
> - HSI (Hive2/HiveServer2 and LLAP) comes up fine.
> - But, hive2/HiveServer2 Thrift port alert check fails. 
> *Current Diagnosis:*
>  
> - The Hive2/HiveServer2 process is running on port 10501, but Alerts tries to check for
port 10500. 



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

Mime
View raw message