Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 20 Nov 2015 19:12:11 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12914853.1448028008000.140491.1448046731455@Atlassian.JIRA>
In-Reply-To: <JIRA.12914853.1448028008000@Atlassian.JIRA>
References: <JIRA.12914853.1448028008000@Atlassian.JIRA>
 <JIRA.12914853.1448028008098@arcas>
Subject: [jira] [Commented] (AMBARI-13994) HiveServer2 Process critical
 alert is present (Upgrade from 2.1.1 to 2.1.3.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on AMBARI-13994:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3877 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3877/])
AMBARI-13994. HiveServer2 Process critical alert is present (Upgrade (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=397ddb59652ee8b5cf4be0d7c3e761a6679e0831])
* ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py


> HiveServer2 Process critical alert is present (Upgrade from 2.1.1 to 2.1.3.0)
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-13994
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13994
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13994.patch
>
>
> We need to relax the check and drop -e 'Error' at the end. The reasoning is as follows:
> Longer term, Hive should provide better ways for Ambari to do health checks. Per Hive committers, some work is going on to expose hiveserver2 metrics that will help with that. In fact, this is just one of the problems of this way of doing health checks. If any of the authentication modes in hive that require passwords is enabled, then connection attempts by this user would still fail. The ambari-qa user being used to perform health checks may not be present in the ID store. So in long term, ambari should move away from using ambari-qa user and rely on HS2 metrics for health check.
> Possible fix for user:
> we should check if user anonymous is available and belongs to proxyuser.groups group. Beside this, user hive should be in proxyuser.group too. In that case everything will work fine.


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