Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4340 | 06-11-2020 02:45 PM | |
5944 | 05-01-2020 12:23 AM | |
3772 | 04-21-2020 03:38 PM | |
4041 | 04-14-2020 12:26 AM | |
3013 | 02-27-2020 05:51 PM |
09-01-2019
05:42 AM
Thanks @Shelton for your info. But @kal 's command got message "Key table file '/etc/security/keytabs/hive.service.keytab' not found", so I am not sure if it is relevant. Cheers
... View more
08-31-2019
09:18 PM
Does Hive use this keytab file: /etc/security/keytabs/hive.service.keytab? I can see klist complained that the file was not found: klist: Key table file '/etc/security/keytabs/hive.service.keytab' not found while starting keytab scan Can you please confirm the permission of the file? ls -al /etc/security/keytabs/hive.service.keytab Cheers Eric
... View more
08-30-2019
06:04 PM
1 Kudo
@Kai, Error message "Client not found in Kerberos database" can happen due to below reasons: - The principal listed (HTTP/host@realm for example) does not exist in the keytab - The case of the principal/host we're connecting with does not match the case of the principal/host in the keytab (Kerberos is case sensitive) - The principal does not exist in the KDC. Note: This sometimes happens because a principal is configured in one AD instance but you are querying another (perhaps through a VIP) and the principal has not yet been replicated. - Multiple entries for the same principal exist in an Active Directory KDC (this breaks subsequent kinit attempts) Please review and see if any of above could be the cause in your case. Cheers Eric
... View more
08-30-2019
05:50 PM
1 Kudo
@Zane- There is some troubleshooting guide in the link below: https://www.cloudera.com/documentation/enterprise/latest/topics/impala_troubleshooting.html which can help a bit. I have also wrote some impala profile tutorial, which can be found below: https://www.ericlin.me/2018/09/impala-query-profile-explained-part-1/ https://www.ericlin.me/2019/04/impala-query-profile-explained-part-2/ https://www.ericlin.me/2019/05/impala-query-profile-explained-part-3/ Hope they can be helpful. Cheers Eric
... View more
08-30-2019
05:48 PM
@LeonanCarvalho In order to find out why it takes time, you need to look at the AM log, see at what stage it was hung and maybe try to get the jstacks of both AM and HS2 to see which thread might be blocking and cause the hang. 6 minutes timeout is a bit long. Is your data quite big? Cheers Eric
... View more
08-30-2019
12:54 AM
@iamabug The principal names are generated based on host's actual FULL qualified domain name, so it has to match with actual hostname, otherwise Kerberos will not work. So what you want in my opinion will not work, as kerberos is quite fuzzy about DNS resolutions. Cheers Eric
... View more
08-29-2019
11:11 PM
@RobbbyG, I don't see this feature is on the pipeline yet, but you can workaround it by kinit manually before your ODBC connection, please see the doc here: https://www.cloudera.com/documentation/other/connectors/hive-odbc/latest/Cloudera-ODBC-Driver-for-Apache-Hive-Install-Guide.pdf and search for "To obtain a ticket for a Kerberos principal using a keytab file:". Cheers Eric
... View more
08-29-2019
04:25 PM
It is same as another profile, please see my response here: https://community.cloudera.com/t5/Support-Questions/ExecQueryFInstances-rpc-query-id-e74ef8d9b9215369/m-p/269400/highlight/true#M206803
... View more
08-29-2019
04:22 PM
@Zane, The issues I can see from this profile as below: 1. The query got closed due to client inactivity: Query f64da6a899944136:22dcac6800000000 expired due to client inactivity (timeout is 10m) Not because of OOM 2. you do not have table stats, which can cause impala to use bad query plan: WARNING: The following tables are missing relevant table and/or column statistics. external_data.physician_compare This is evident that in the SUMMARY section, the estimated rows are -1: Operator #Hosts Avg Time Max Time #Rows Est. #Rows Peak Mem Est. Peak Mem Detail -------------------------------------------------------------------------------------------------------------------------- 01:EXCHANGE 1 189.890ms 189.890ms 1.02K -1 0 0 UNPARTITIONED 00:SCAN HDFS 5 98.859ms 104.753ms 22.53K -1 78.33 MB 176.00 MB external_data.physician_compare 3. Query finished in about 1 second, as result was ready after 1.45 seconds: First row fetched: 1.45s 4. I can see the query is most likely from hue: Session Type: HIVESERVER2 So my conclusion is that user stayed in Hue Hive editor idle until query is closed from server side. There is no issue from the query itself whatsoever. Cheers
... View more
08-29-2019
04:13 PM
Running Impala query over driver from Spark is not currently supported by Cloudera. Why don't you just use SparkSQL instead? Why need to have extra layer of impala here? Cheers Eric
... View more