You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jayush Luniya (JIRA)" <ji...@apache.org> on 2018/10/22 21:01:08 UTC
[jira] [Updated] (AMBARI-24582) Ambari Alert - HiveServer2 Process
- False negative in Certain Scenarios
[ https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayush Luniya updated AMBARI-24582:
-----------------------------------
Fix Version/s: (was: 2.7.2)
2.7.3
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
> ------------------------------------------------------------------------
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as permission problems and SSL/JKS problems. Instead, we should change this to a positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:10000/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:10000/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)