You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/04 01:00:57 UTC

[jira] [Updated] (HDFS-4477) Secondary namenode may retain old tokens

     [ https://issues.apache.org/jira/browse/HDFS-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated HDFS-4477:
-----------------------------------
    Fix Version/s:     (was: 3.0.0)

> 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
>             Fix For: 2.1.0-beta, 0.23.8
>
>         Attachments: HDFS-4477.branch-23.patch, HDFS-4477.patch, HDFS-4477.patch, HDFS-4477.patch, 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 was sent by Atlassian JIRA
(v6.3.4#6332)