[HDFS-4477] Secondary namenode may retain old tokens

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.0, 2.0.0-alpha, 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta, 0.23.8
• Component/s: security
• Target Version/s: 2.1.0-beta
• Hadoop Flags: Reviewed
• Assignee: Daryn Sharp
• Reporter: Kihwal Lee
• Created: 07/Feb/13 17:01
• Updated: 06/Feb/18 17:33
• Resolved: 16/May/13 19:14

Description

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.

Issue Links

• causes: HDFS-13112 Token expiration edits may cause log corruption or deadlock
• is blocked by: HDFS-4690 Namenode exits if entering safemode while secret manager is edit logging
• relates to: HADOOP-9341 Secret Managers should allow explicit purging of tokens and secret keys

Sub-Tasks

• Secret manager saves expired items: Resolved