[
https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118155#comment-15118155
]
Arpit Agarwal edited comment on HADOOP-12664 at 1/26/16 10:52 PM:
------------------------------------------------------------------
# {{verifyKinitExecutable}} can return a reference to the kinit executable as
Steve suggests below.
# {{verifyKinitExecutable}} should be called before launching the renewal
thread as we want the exception to go to the caller. I think the effect will be
backwards-incompatible for broken deployments so we can catch the exception and
log an error for 2.x. For 3.x we can let the exception propagate to the caller.
# I don't recall if ERROR messages from the UGI logger show up by default or
not. If not we should fix that too, perhaps as part of HADOOP-12649.
was (Author: arpitagarwal):
# {{verifyKinitExecutable}} can have a return type of void since it throws
exceptions on all failure paths.
# {{verifyKinitExecutable}} should be called before launching the renewal
thread as we want the exception to go to the caller. I think the effect will be
backwards-incompatible for broken deployments so we can catch the exception and
log an error for 2.x. For 3.x we can let the exception propagate to the caller.
# I don't recall if ERROR messages from the UGI logger show up by default or
not. If not we should fix that too, perhaps as part of HADOOP-12649.
> 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)
