Daryn Sharp commented on HADOOP-15593:

The solution is probably call {{KerberosTicket#isDestroyed}} before checking 
the end time.

However, this shouldn't cause issues for the RM unless there's another bug.  
The renewer is only used when a login uses a ticket cache.  No server process 
should be using a ticket cache or you will be in for a rude surprise if 
something uses the RM unix user to kinit as a different user, or does a 

> UserGroupInformation TGT renewer throws NPE
> -------------------------------------------
>                 Key: HADOOP-15593
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15593
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Gabor Bota
>            Priority: Critical
> Found the following NPE thrown in UGI tgt renewer. The NPE was thrown within 
> an exception handler so the original exception was hidden, though it's likely 
> caused by expired tgt.
> {noformat}
> 18/07/02 10:30:57 ERROR util.SparkUncaughtExceptionHandler: Uncaught 
> exception in thread Thread[TGT Renewer for f...@example.com,5,main]
> java.lang.NullPointerException
>         at 
> javax.security.auth.kerberos.KerberosTicket.getEndTime(KerberosTicket.java:482)
>         at 
> org.apache.hadoop.security.UserGroupInformation$1.run(UserGroupInformation.java:894)
>         at java.lang.Thread.run(Thread.java:748){noformat}
> Suspect it's related to [https://bugs.openjdk.java.net/browse/JDK-8154889].
> The relevant code was added in HADOOP-13590. File this jira to handle the 
> exception better.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to