About alex_goron

alex_goron · ‎11-02-2018

After doing some more research on the absence of valid TGT, I found that the issue was really in default_ccache_name set to KEYRING:persistent:%{uid} in krb5.conf . I realized that I'm hitting this specific issue while reading this thread. For whatever reason Hadoop has an issue with the KEYRING. So setting default_ccache_name to FILE has resolved this issue and appropriate TGT are being provided now and NameNode does not take that much time to start and does not fail anymore. My updated parameter looks like like this: default_ccache_name=FILE:/tmp/krb5cc_%{uid} I have also propagated the config file throughout the cluster.

alex_goron · ‎10-26-2018

@Jay Kumar SenSharma, Thanks a lot for helping me! Aparently I ran out of inodes. Not sure why it did not occur to me to check it first place ... Anyways reformatting the filesystem and a little bit of file shuffling exercise did the trick 🙂

jsensharma · ‎10-30-2018

@Geoffrey Shelton Okot Only a user who own the thread Or a user with 1000+ points can accept other users answers as accepted. I have marked your previous answer as "Accepted" which you answered on "Aug 09, 2017" as that answer looks more informative form this HCC thread perspective.

Shelton · ‎10-21-2018

@Robert Levas @Alex Goron How about the functionality of managing remote cluster? Personally I haven't implemented that but you can register and manage a remote cluster!

Online	Offline
Last Visited	‎03-20-2019 06:12 PM

Member Since	‎07-26-2018 04:04 AM
Last Visited	‎03-20-2019 06:12 PM
Posts	25
Kudos received	1

Cloudera Community

Re: Long startup time for NameNode

Re: Long startup time for NameNode

Re: ambari-metrics-collector : resource_management...

Re: Kerberos Setup on HDP 2.6

Re: Multiple clusters on Ambari