You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/02/01 16:47:39 UTC
[jira] [Commented] (HADOOP-12664) UGI auto-renewer does not verify
kinit availability during initialization
[ https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126420#comment-15126420 ]
Steve Loughran commented on HADOOP-12664:
-----------------------------------------
UGI @ error does log, BTW
> 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
> Labels: supportability
> 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)