Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <7924727.290741294771486403.JavaMail.jira@thor>
Date: Tue, 11 Jan 2011 13:44:46 -0500 (EST)
From: "Kan Zhang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
 even if TGT can't be found
In-Reply-To: <1342179.200091294353645366.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980245#action_12980245 ] 

Kan Zhang commented on HADOOP-7091:
-----------------------------------

> Hi Kan, should this have gone in the 0.22 branch as well?
Yes. Can you help me get it committed? Thanks!

> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
>                 Key: HADOOP-7091
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7091
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>             Fix For: 0.23.0
>
>         Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.