[ https://issues.apache.org/jira/browse/HAWQ-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387063#comment-15387063 ]
ASF GitHub Bot commented on HAWQ-940: ------------------------------------- Github user linwen commented on the issue: https://github.com/apache/incubator-hawq/pull/804 After re-think this fix, I think it's better to check ticket expiration in resource broker process loop. so close it. > 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: Lei Chang > 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)