[
https://issues.apache.org/jira/browse/AMBARI-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-13994:
---------------------------------------
Attachment: AMBARI-13994.patch
> 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)
