[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios

2018-11-14 Thread Jonathan Hurley (JIRA) 


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

Jonathan Hurley commented on AMBARI-24582:
--

This check is used for all cases, including Kerberos. Ambari does pass a 
credential string when connecting. Can you elaborate more on the HS2 
username/password case you are referring to?

> 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:1/;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:1/;transportMode=binary
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios

2018-11-13 Thread Thejas M Nair (JIRA) 


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

Thejas M Nair commented on AMBARI-24582:


[~jonathan.hurley]
AFAIK, Ambari hasn't had a mechanism to specify username/password to connection 
HS2, when HS2 is using username/password based authentication.
So it will fail to connect and do a positive healthcheck in such scenarios.
Is this positive check being enabled only for non password based authentication 
cases ?

> 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:1/;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:1/;transportMode=binary
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios

2018-08-31 Thread Hudson (JIRA) 


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

Hudson commented on AMBARI-24582:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9908 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/9908/])
[AMBARI-24582] - Ambari Alert - HiveServer2 Process - False negative in 
(jonathanhurley: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a4b2901a9a16e356c230fb647471e099b2d965ba])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py


> 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.2
>
>  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:1/;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:1/;transportMode=binary
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios

2018-08-31 Thread Hudson (JIRA) 


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

Hudson commented on AMBARI-24582:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #213 (See 
[https://builds.apache.org/job/Ambari-branch-2.7/213/])
[AMBARI-24582] - Ambari Alert - HiveServer2 Process - False negative in 
(jonathanhurley: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5cadc1d2ce6bc11e07f106c03466342a345919e4])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_interactive_thrift_port.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py


> 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.2
>
>  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:1/;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:1/;transportMode=binary
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)