[
https://issues.apache.org/jira/browse/HADOOP-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802763#comment-15802763
]
Allen Wittenauer commented on HADOOP-12664:
-------------------------------------------
If you are generalizing this code for Shell, definitely.
For kinit, specifically, I'm not really sure why we need to do all of this work
when it just seems like the problem is that we're not checking the exit code or
trying to catch the exception of:
{code}
Shell.execCommand(cmd, "-R");
{code}
In fact, this patch seems to have the same problem: it just assumes that the -R
is going to succeed.
> 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, HADOOP-12664.002.patch,
> HADOOP-12664.003.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
