Created on 09-07-2016 11:34 AM - edited 08-19-2019 01:20 AM
Created 09-07-2016 09:16 PM
I assume your cluster is kerberized. The token seems expired. You need to ask your admin to check why the token is expired and avoid that event going forward.
A good start to understand Kerberos and how it works is the documentation: https://docs.hortonworks.com/HDPDocuments/Ambari-188.8.131.52/bk_Ambari_Security_Guide/content/ch_configu...
If any of the responses to your question addressed the problem don't forget to vote and accept the answer. If you fix the issue on your own, don't forget to post the answer to your own question. A moderator will review it and accept it.
Created 09-09-2016 02:40 PM
Thanks for you reply. Yes, I'm trying to find out why Yarn can't renew the token.Sure, I'll definitely post answer while I sort this out.
Created 09-07-2016 09:32 PM
I agree with @Constantin Stanca that you are accessing a Kerberized cluster and you don't have proper setup. The error you see is "Impersoation does not exist". Here is how I will try. You need to kinit using a keytab which I think you are already doing. That being said, you are running as user root. "root" apparently does not have access to hive. Right now assuming you are doing kinit before running "hive" command (not shown in your screenshot), here is how this would work.
kinit -k -t /path/to/hive.keytab hive/_HOST@REALM.COM //I am assuming you did this already. Just not shown in your screen shot. "sudo -u hive hive" //the first hive is user hive and second is command hive.
This should work. But if you want other users to access hive, you will need to enable impersonation and then run with appropriate users.
Created 09-09-2016 02:45 PM
Thanks for your reply. There is no hive user on my VM. Should I create a hive user and change the owner of hive client directories from root to hive? I did all hdp client setup with the root user.