You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vrushali C (JIRA)" <ji...@apache.org> on 2018/01/25 19:18:00 UTC
[jira] [Commented] (YARN-7765) [Atsv2] GSSException: No valid
credentials provided - Failed to find any Kerberos tgt thrown by
HBaseClient in NM and HDFSClient in HBase daemons
[ https://issues.apache.org/jira/browse/YARN-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339674#comment-16339674 ]
Vrushali C commented on YARN-7765:
----------------------------------
It looks like this is happening to long running hbase connections like in this case from the timeline collector in the Node Manager to hbase. The hbase connection does not "automatically" pick the new kerberbos information after the lifetime expiration. Perhaps we can consider adding a connection expiry when we set up the hbase connection in the timeline collector.
> [Atsv2] GSSException: No valid credentials provided - Failed to find any Kerberos tgt thrown by HBaseClient in NM and HDFSClient in HBase daemons
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-7765
> URL: https://issues.apache.org/jira/browse/YARN-7765
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Priority: Critical
>
> Secure cluster is deployed and all YARN services are started successfully. When application is submitted, app collectors which is started as aux-service throwing below exception. But this exception is *NOT* observed from RM TimelineCollector.
> Cluster is deployed with Hadoop-3.0 and Hbase-1.2.6 secure cluster. All the YARN and HBase service are started and working perfectly fine. After 24 hours i.e when token lifetime is expired, HBaseClient in NM and HDFSClient in HMaster and HRegionServer started getting this error. After sometime, HBase daemons got shutdown. In NM, JVM didn't shutdown but none of the events got published.
> {noformat}
> 2018-01-17 11:04:48,017 FATAL ipc.RpcClientImpl (RpcClientImpl.java:run(684)) - SASL authentication failed. The most likely cause is missing or invalid credentials. Consider 'kinit'.
> javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
> {noformat}
> cc :/ [~vrushalic] [~varun_saxena]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org