@BHASKARA VENNA It's usually advisable to immediately create a local user with a sudoer privilege,this could have been your savior. Depending on your OS check this 2 links you should be able to reset the root password. Ubuntu https://www.maketecheasier.com/reset-root-password-linux/ Centos https://opensource.com/article/18/4/reset-lost-root-password ... View more

@Nathaniel Vala That shows a permission issue on this file /usr/hdp/current/ranger-admin/ews/ranger-admin-services.sh can you check that the file is readable and executable by user ranger and only readable by group and world r-x-r--r-- ... View more

@harish Prerequisite: MUST DO If you want to copy a hive table across to another REALM you need to setup cross-realm trust between two MIT KDC's.This will enable the destination REALM user to have a valid Kerberos ticket to run operations on the source Cluster. Having said that, you should forget to revise your ranger policies to reflect the new REALM access privilege if the Ranger plugin has been enabled in the source cluster which I assume is the case to leverage the Ranger authorization. Here is a link to an HCC document that could help you set up the REALM trust PROCEDURE Follow the steps below to migrate a Hive database from one cluster to another: 1. Install Hive on the new cluster and make sure both the source and destination clusters are identical. 2. Transfer the data present in the Hive warehouse directory (/user/hive/warehouse) to the new Hadoop cluster. hadoop distcp <src> <dst>  3. Take a backup of the Hive Metastore. mysqldump hive > /tmp/mydir/backup_hive.sql 4. Install MySQL on the new Hadoop cluster. 5. Open the Hive MySQL-Metastore dump file and replace the source NameNode hostname with the destination hostname.  hdfs://ip-address-old-namenode:port  ---> hdfs://ip-address-new-namenode:port  6. Restore the edited MySQL dump into the MySQL of new the Hadoop cluster. mysql hive < /tmp/mydir/backup_hive.sql 7. Configure Hive as normal and perform the Hive schema upgrade if needed Impact Hive metadata contains the information about the database objects, and the contents are stored in the Hadoop Distributed File System (HDFS). Metadata contains HDFS URI and other details. Therefore, if you migrate Hive from one cluster to another cluster, you have to point the metadata to the HDFS of the new cluster. If you don't do this, it will point to the HDFS of the older cluster and the migration will fail. In case of any failure, initialize the Hive Metastore of the destination cluster and resume the migration following the correct steps. /bin/schematool -initSchema -dbType mysql  On CDH If you are on Cloudera then you can proceed using Backup and Disaster recovery procedure HTH ... View more

@Michael Bronson HWX doesn't recommend upgrading an individual HDP component because one never knows the incompatibilities that could impact the other components and component selective upgrades tend to be a nightmare during a version upgrade The lastest HDP Kafka version is 11-2.1.x delivered by HDP 3.1 but ASF has its own rollout version and naming convention HTH ... View more

@Manjunath P N The latest HDP 3.1, unfortunately, supports spark 2.3, so you will have to wait for the next major release but after the Cloudera & Hortonworks merger, my best guess is don't expect any new HDP version anytime before the release of the combined new offering Cloudera Data Platform (CDP) sometime in 2020 or thereafter. I would imagine currently HWX and CLDR should be more focused on the integration of the new products than really trying to release a newer version. The new combined offering CDP will be based on HDP 3.x and CDH 5 HTH ... View more