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] [Updated] (HADOOP-12664) UGI auto-renewer does not verify kinit availability during initialization
Date Tue, 26 Jan 2016 00:49:40 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ray Chiang updated HADOOP-12664:
    Attachment: HADOOP-12664.001.patch

Initial patch.
- Moved the configuration variable name plus default to CommonConfigurationKeysPublic
- I couldn't find any APIs that would do the file path checking.  Please let me know if there's
a better way to write the file exists/execute part more cleanly.  I haven't tried writing
a more abstract version for FileUtil.java yet.
- I did *NOT* change the structure of the renewal thread.  This results in the client running
on a bit further past the error.  I wasn't sure about the best way of handling that.

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

View raw message