hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12664) UGI auto-renewer does not verify kinit availability during initialization
Date Tue, 26 Jan 2016 22:11:39 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118159#comment-15118159
] 

Ray Chiang commented on HADOOP-12664:
-------------------------------------

Thanks for all the feedback guys--that gives me much better context for how the design should
look.  I'll see how the refactoring goes and try to get as much of these fixes in as possible.

> 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)

Mime
View raw message