Member since
02-27-2018
4
Posts
0
Kudos Received
0
Solutions
02-27-2018
11:04 PM
Hi Can I get a link to the support article? Or can you let me know the fix that was suggested? Thanks.
... View more
01-23-2018
06:01 AM
We have set up ambari alerts to be written to SNMP following the following article: https://community.hortonworks.com/articles/74370/snmp-alert.html This set up was working fine for us, but for the last 3 days we can see that the alerts are not being picked up by SNMP traps. The snmp daemon is running and the alerts are appearing on ambari-alerts.log. How can I check where the issue is and how can this be rectified? Regards, Pranav Lal
... View more
Labels:
01-16-2018
09:14 AM
There are no errors/messages regarding the login attempt in hiveserver2.log, that is, the attempt is not reflecting in the logs at all. Could it be failing at a step before actually hitting hive?
... View more
01-16-2018
08:56 AM
We have a kerberized cluster with Jupyterhub installed on one of the edge nodes. When trying to lauch beeline using zookeeper service discovery mode on a jupyterhub terminal, we ge the below error: Error: Could not open client transport for any of the Server URI's in ZooKeeper: Unable to read HiveServer2 uri from ZooKeeper (state=08S01,code
=0) When using a beeline connection string to hit the hiveserver2 directly (HTTP mode), we get the following error: java.sql.SQLException: Could not open client transport with JDBC Uri: jdbc:hive2://managenode1:10001/default;transportMode= http;httpPath=cliservice;principal=hive/_HOST@GLOBAL.REALM;: Could not create http connection to jdbc:hive2://managenode1:10001/default;transportMode=http;httpPath=cliservice;principal=hive/_HOST@GLOBAL.REALM;. org.apache.http.client.ClientProtocolException at org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:231) . . Caused by: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt) I have a kerberos ticket created and I am able to query HDFS filesystem and launch hive shell from the same terminal. The beeline connection strings used are also correct, since we are able to login to beeline using these strings when connecting to the server directly via Putty. It is only on the beeline terminal that we are facing this issue. Any suggestions?
... View more
Labels: