[
https://issues.apache.org/jira/browse/HDFS-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863333#comment-13863333
]
Hudson commented on HDFS-5589:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4961 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4961/])
HDFS-5589. Namenode loops caching and uncaching when data should be uncached.
(awang via cmccabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1555996)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/CacheReplicationMonitor.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestFsDatasetCache.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestCacheDirectives.java
> Namenode loops caching and uncaching when data should be uncached
> -----------------------------------------------------------------
>
> Key: HDFS-5589
> URL: https://issues.apache.org/jira/browse/HDFS-5589
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: caching, namenode
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: hdfs-5589-1.patch, hdfs-5589-2.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
