@Harry Li The mentioned error and the stack trace of the error indicates that you might be using a higher version of mysql-connector-java JDBC Driver. As the new API " com.mysql.cj " can be seen in the StackTrace. https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-api-changes.html This section describes the changes to the Connector/J API going from version 5.1 to 6.0 / 8.0. You might need to adjust your API calls accordingly: The name of the class that implements java.sql.Driver in MySQL Connector/J has changed from com.mysql.jdbc.Driver to com.mysql.cj.jdbc.Driver . The old class name has been deprecated. The names of these commonly-used interfaces have also been changed: ExceptionInterceptor: from com.mysql.jdbc.ExceptionInterceptor to com.mysql.cj.exceptions.ExceptionInterceptor StatementInterceptor: from com.mysql.jdbc.StatementInterceptorV2 to com.mysql.cj.interceptors.QueryInterceptor ConnectionLifecycleInterceptor: from com.mysql.jdbc.ConnectionLifecycleInterceptor to com.mysql.cj.jdbc.interceptors.ConnectionLifecycleInterceptor AuthenticationPlugin: from com.mysql.jdbc.AuthenticationPlugin to com.mysql.cj.protocol.AuthenticationPlugin BalanceStrategy: from com.mysql.jdbc.BalanceStrategy to com.mysql.cj.jdbc.ha.BalanceStrategy . . Please make sure that you are using the correct MySQL JDBC driver. Like if you are using HDP 2.6.5 then MySQL 5.7 Database and respective JDBC driver version needs to be used. . ... View more

@Maxim Neaga What error are you gettin while connecting to hive using beeling? Are you sure that the URL which you entered is correct... Becaue looks like you are trying to connect to MySQL database instead of hiveServer2. Following is what i tried: # useradd test # usermod -G hadoop test # su - hdfs -c "hdfs dfs -mkdir /user/test" # su - hdfs -c "hdfs dfs -chown -R test:hadoop /user/test" . The connect to Beeline using test user: # su - test $ beeline Beeline version 1.2.1000.2.6.5.0-292 by Apache Hive beeline> !connect jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2 . Execute queries: beeline> !connect jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2 Connecting to jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2 Enter username for jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2: Enter password for jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2: Connected to: Apache Hive (version 1.2.1000.2.6.5.0-292) Driver: Hive JDBC (version 1.2.1000.2.6.5.0-292) Transaction isolation: TRANSACTION_REPEATABLE_READ 0: jdbc:hive2://newhwx1.example.com:2181,newh> show databases; +----------------+--+ | database_name | +----------------+--+ | default | +----------------+--+ 1 row selected (0.627 seconds) Here the URL needs to be correct. For example in above case i am connecting to HiveServer2 using the Zookeepre quorum which i found in the Ambari Hive Summary page. jdbc:hive2://newhwx1.example.com:2181,newhwx2.example.com:2181,newhwx3.example.com:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2 . Hive URL you can get from here in Ambari UI: . ... View more

@Michael Bronson The latest version of HDP is currently HDP 3.0, Which is already released. If you want to know the New Features added as part of HDP 3.0 then you can refer to the following docs: New Features HDP 3.0: https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.0/release-notes/content/new_features.html Behavior Changes in HDP 3.0: https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.0/release-notes/content/behavior_changes.html Overview of all changes/fixes/known issues of HDP 3.0 can be found here: Release Notes HDP 3.0: https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.0/release-notes/content/relnotes.html . Similarly if you wanted to know the behavior changes/Fixes that happened in HDP 2.6,5 then this information can be found at the Release Notes page of the HDP 2.6.5 doc. https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_release-notes/content/ch_relnotes.html ... View more

@Sam Red When you will run the following command then you will find a property in the output as an example "-Djava.security.krb5.conf=/etc/krb5.conf" which ambari is using. # ps -ef | grep AmbariServer Please open that file which is mentioned in the property "java.security.krb5.conf" and findout what is the Address of KDC # grep -A3 '\[realms\]' /etc/krb5.conf In the above output whatever KDC hostname you get try to ping the KDC host & Port like following from ambari server host and verify if it is able to connect to port 88 (default port of KDC): One Ambari Server Host # ping $KDC_HOST # nc -v $KDC_HOST 88 If you find any connectivity issue when running the above command from Ambari Server host then you should login in to KDC host and verify if the Firewall is disabled and Port 88 is opened or not? . Also find the ambari Keytab and get the principal name # grep 'keyTab' /etc/ambari-server/conf/krb5JAASLogin.conf # klist -kte /etc/security/keytabs/ambari.server.keytab Now verify if ytou are able to get a valid kerberos ticket using the mentioned keytab or not? (this will help in isolating any issue with KDC or ticket retrival) # kinit -kt /etc/security/keytabs/ambari.server.keytab $AMBARI_PRINCIPAL_FROM_ABOVE_COMMAND On KDC Host # netstat -tnlpa | grep 88 # service iptables stop # service krb5kdc restart . ... View more

@Harry Li It looks like a Symlink issue. Looks like due to some reason the symlink is not created properly. The "lib" should be actually here # ls -l /usr/hdp/2.6.5.0-292/slider/lib/ . The "/usr/hdp/current/slider-client" path should be ideally a symlink something like following: # ls -l /usr/hdp/current/slider-client lrwxrwxrwx. 1 root root 27 Jun 28 22:44 /usr/hdp/current/slider-client -> /usr/hdp/2.6.5.0-292/slider NOTE: here the version "2.6.5.0-292" might be different based on your Stack version. So please change the version accordingly. . So you might want to create a symlink on your own. First if you have "slider-client" as a Directory or as a Symlink? # ls -ld /usr/hdp/current/slider-client lrwxrwxrwx. 1 root root 27 Jun 28 22:44 /usr/hdp/current/slider-client -> /usr/hdp/2.6.5.0-292/slider If you find that "/usr/hdp/current/slider-client" is a directory then move it. # mv /usr/hdp/current/slider-client /usr/hdp/current/slider-client_OLD Then create a symlink instead like: # ln -s /usr/hdp/2.6.5.0-292/slider /usr/hdp/current/slider-client NOTE: here the version "2.6.5.0-292" might be different based on your Stack version. So please change the version accordingly. . ... View more

@Fawad Shah You will need to make sure that you have logged in to the Sandbox Terminal using SSH port 2222 ( not on port 22) as the Sandbox is a dockerized container inside the VM. So pelase try any of the following approach: 1. Do SSH login to Sandbox on port 2222 then check the mentioned file. # ssh root@127.0.0.1 -p 2222 Enter Password: hadoop 2. The alternate option will be to use the Web Terminal using Web Browser: http://127.0.0.1:4200 Enter Password: hadoop . ... View more