Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 28 Feb 2013 16:43:13 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12631303.1360256507114.358464.1362069793297@arcas>
In-Reply-To: <JIRA.12631303.1360256507114@arcas>
References: <JIRA.12631303.1360256507114@arcas>
Subject: [jira] [Commented] (HDFS-4477) Secondary namenode may retain old
 tokens
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589651#comment-13589651 ] 

Daryn Sharp commented on HDFS-4477:
-----------------------------------

After a discussion/agreement with Suresh, I'm implementing a quick fix for the 2NN with HADOOP-9341 and HDFS-4539.  These changes will not address HA issues.

I do believe the best long-term solution is to treat token expiration identical to token cancellation.  We know the latter works, and won't require any special case handling of expiration.  This jira will remain open until the comprehensive solution is implemented.
                
> Secondary namenode may retain old tokens
> ----------------------------------------
>
>                 Key: HDFS-4477
>                 URL: https://issues.apache.org/jira/browse/HDFS-4477
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Kihwal Lee
>            Assignee: Daryn Sharp
>            Priority: Critical
>         Attachments: HDFS-4477.patch, HDFS-4477.patch
>
>
> Upon inspection of a fsimage created by a secondary namenode, we've discovered it contains very old tokens. These are probably the ones that were not explicitly canceled.  It may be related to the optimization done to avoid loading fsimage from scratch every time checkpointing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira