[
https://issues.apache.org/jira/browse/HAWQ-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387079#comment-15387079
]
ASF GitHub Bot commented on HAWQ-940:
-------------------------------------
Github user linwen commented on the issue:
https://github.com/apache/incubator-hawq/pull/804
Another way of fix is to add the ticket check in resource broker process
loop, for every time interval, login() is called. But this fix has to keep
another variable to record the last updated time, which is duplicate with
login().
> Kerberos Ticket Expired for LibYARN Operations
> ----------------------------------------------
>
> Key: HAWQ-940
> URL: https://issues.apache.org/jira/browse/HAWQ-940
> Project: Apache HAWQ
> Issue Type: Bug
> Components: libyarn
> Reporter: Lin Wen
> Assignee: Lin Wen
> Fix For: 2.0.1.0-incubating
>
>
> HAWQ's libhdfs3 and libyarn use a same kerberos keyfile.
> Whenever a hdfs operation is triggered, a function named login() is called,
> in login() function, this ticket is initialized by "kinit".
> But for libyarn, login() function is only called during the resource broker
> process starts. So if HAWQ starts up and there is no query for a long
> period(24 hours in kerberos's configure file, krb.conf), this ticket will
> expire, and HAWQ fails to register itself in Hadoop YARN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
