[
https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117657#comment-15117657
]
Steve Loughran commented on HADOOP-12664:
-----------------------------------------
...I mean `kinit.exe` Which, on my test machine, comes from {{%JAVA
_HOME%\bin}}. even though according to
[MSDN|https://technet.microsoft.com/en-us/library/hh134826.aspx], there's a
klist shipping with windows 8+
UGI/KDIag should print out the location of the kinit/klist commands
{code}
C:\>%JAVA_HOME%\bin\klist
Credentials cache C:\Users\Administrator\krb5cc_Administrator not found.
C:\>%JAVA_HOME%\bin\kinit
Exception: Can not obtain principal name
java.lang.IllegalArgumentException: Can not obtain principal name
at sun.security.krb5.internal.tools.Kinit.<init>(Kinit.java:162)
at sun.security.krb5.internal.tools.Kinit.main(Kinit.java:113)
C:\>c:\Windows\system32\klist
Current LogonId is 0:0x36f65
Cached Tickets: (0)
C:\>c:\Windows\system32\kinit
'c:\Windows\system32\kinit' is not recognized as an internal or external
command,
operable program or batch file.
{code}
> UGI auto-renewer does not verify kinit availability during initialization
> -------------------------------------------------------------------------
>
> Key: HADOOP-12664
> URL: https://issues.apache.org/jira/browse/HADOOP-12664
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Arpit Agarwal
> Assignee: Ray Chiang
> Priority: Minor
> Attachments: HADOOP-12664.001.patch
>
>
> UGI auto-renewer does not verify that {{hadoop.kerberos.kinit.command}} is in
> the path during initialization. If not available, the auto-renewal thread
> will hit an error during TGT renewal. We recently saw a case where it
> manifests as transient errors during client program execution which can be
> hard to track down without UGI logging.
> It seems like {{kinit}} availability should be verified during initialization
> to make the behavior more predictable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
