hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5589) Namenode loops caching and uncaching when data should be uncached
Date Fri, 03 Jan 2014 02:40:50 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Wang updated HDFS-5589:
------------------------------

    Attachment: hdfs-5589-1.patch

Patch attached. The cache/uncache bug was that we weren't clearing out blocks that weren't
marked during the directive scan. So, an orphan block would retain the old mark and replication
factor, and become cached again on the next rescan when the mark flipped to the old value.

I also incorporated HDFS-5507 (considering stale and capacity when caching), and also fixed
another bug I found where we'd try to cache a block again on a node that already had it cached.


> 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
>         Attachments: hdfs-5589-1.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)

Mime
View raw message