[HDFS-3835] Long-lived 2NN cannot perform a checkpoint if security is enabled and the NN restarts with outstanding delegation tokens

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.0.2-alpha
• Component/s: namenode, security
• Target Version/s: 2.0.2-alpha
• Hadoop Flags: Reviewed
• Assignee: Aaron Myers
• Reporter: Aaron Myers
• Created: 22/Aug/12 01:18
• Updated: 11/Oct/12 17:46
• Resolved: 22/Aug/12 18:59

Description

When the 2NN wants to perform a checkpoint, it figures out the highest transaction ID of the fsimage files on the NN, and if the 2NN has a copy of that fsimage file (because it created that merged fsimage file the last time it did a checkpoint) then the 2NN won't download the fsimage file from the NN, and instead only gets the new edits files from the NN. In this case, the 2NN also doesn't even bother reloading the fsimage file it has from disk, since it has all of the namespace state in-memory. This all works just fine.

When the 2NN doesn't have a copy of the relevant fsimage file (for example, if the NN had restarted since the last checkpoint) then the 2NN blows away its in-memory namespace state, downloads the fsimage file from the NN, and loads the newly-downloaded fsimage file from disk. The bug is that when the 2NN clears its in-memory state, it only resets the namespace, but not the delegation token map.

The fix is pretty simple - just make the delegation token map get cleared as well as the namespace state when a running 2NN needs to load a new fsimage from disk.

Credit to Stephen Chu for identifying this issue.

Issue Links

• is related to: HDFS-3849 When re-loading the FSImage, we should clear the existing genStamp and leases.