[HDFS-5589] Namenode loops caching and uncaching when data should be uncached

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.3.0
• Component/s: caching, namenode
• Assignee: Andrew Wang
• Reporter: Andrew Wang
• Created: 02/Dec/13 19:29
• Updated: 12/May/16 18:14
• Resolved: 10/Jan/14 01:17

Description

This was reported by cnauroth and brandonli, and schu repro'd it too.

If you add a new caching directive then remove it, the Namenode will sometimes get stuck in a loop where it sends DNA_CACHE and then DNA_UNCACHE repeatedly to the datanodes where the data was previously cached.

Issue Links

• is duplicated by: HDFS-5507 Consider maximum DN memory, stale status when scheduling recaching