[
https://issues.apache.org/jira/browse/HDFS-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586225#comment-13586225
]
Daryn Sharp commented on HDFS-4477:
-----------------------------------
Per my first comment, my initial thought was to ignore expired tokens when
writing the image. However, won't HA NNs in standby accumulate expired tokens
and secrets until they go active and their TSM thread is activated to remove
expired tokens & secrets?
> 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
