You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/20 09:26:20 UTC
[jira] [Commented] (HAWQ-940) Kerberos Ticket Expired for LibYARN
Operations
[ https://issues.apache.org/jira/browse/HAWQ-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385590#comment-15385590 ]
ASF GitHub Bot commented on HAWQ-940:
-------------------------------------
GitHub user linwen opened a pull request:
https://github.com/apache/incubator-hawq/pull/804
HAWQ-940. Fix Kerberos ticket expired for libyarn operations
Please review, thanks!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/linwen/incubator-hawq hawq_940
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/804.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #804
----
commit 0942630825f6c84da155bd2d9aec4831f7e4d049
Author: Wen Lin <wl...@pivotal.io>
Date: 2016-07-20T09:07:01Z
HAWQ-940. Fix Kerberos ticket expired for libyarn operations
----
> 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)