You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lin Wen (JIRA)" <ji...@apache.org> on 2016/07/21 03:25:20 UTC
[jira] [Assigned] (HAWQ-940) Kerberos Ticket Expired for LibYARN
Operations
[ https://issues.apache.org/jira/browse/HAWQ-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Wen reassigned HAWQ-940:
----------------------------
Assignee: Lin Wen (was: Lei Chang)
> 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)