@dmharshit  Please have a look at my other posting on keytabs https://community.cloudera.com/t5/Support-Questions/Headless-Keytab-Vs-User-Keytab-Vs-Service-Keytab/m-p/175277/highlight/true#M137536 Having said that you are switched to the hive user and attempting to use hdfs-headless-keytab. That's not possible. As the root user run the following steps # su - hdfs [hdfs@server-hdp ~]$ kinit -kt /etc/security/keytabs/hdfs.headless.keytab Now you should have a valid ticket [hdfs@server-hdp ~]$ klist Happy hadooping !!!   ... View more

since you have specified the target location in hdfs, you can create a table to read the data from the hdfs location. Also you can import to infer schema from the DB. sqoop import --connect jdbc:mysql://mysql_localhost/schema_database \ --username sqoop \ --table visits --password '*******' --hive-import --create-hive-table --hive-table Hive_database.visits -m 1 ... View more

Nice piece, Can you snapshot to a location outside the repository? ... View more

@kwabstian53  Also as we see that the webhdfs call is actually failing with 404 (resource not found) hence it will be good to find which resource is it ... gthen later we can chekc why it does not exist on HDFS> We can try grepping the "webhdfs' in the Active NameNode HDFS Audit log exactly when we notice  'HDFS Service check failure' We can grep the logs as following: # grep 'proto\=webhdfs' /var/log/hadoop/hdfs/hdfs-audit.log   So when the hdfs service check will fail then exactly at the same time we will know why it failed and for which resource. .   ... View more