hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12664) UGI auto-renewer does not verify kinit availability during initialization
Date Tue, 23 Feb 2016 17:26:18 GMT

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

Steve Loughran commented on HADOOP-12664:

another thought reviewing this again. What if there is a directory kinit/ under a path dir,
e.g. {{/usr/bin/kinit}}, while elsewhere there's a kinit binary {{/usr/local/bin/kinit}}.
I believe that the OS will skip the dir and look for the binary, only failing if it's not
found. Whereas the current scanner will fail if the path exists but isn't executable. I think
it should skip directories.

Maybe this could be factored out into a unit "FindExecutable" method? It could look for different
exes elsewhere (we could look for javac as a unit test)?

> 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

View raw message