[jira] [Resolved] (HDFS-5203) Concurrent clients that add a cache directive on the same path may prematurely uncache from each other.

["Colin Patrick McCabe (JIRA)" <ji...@apache.org>]

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

Colin Patrick McCabe resolved HDFS-5203.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: HDFS-4949

> Concurrent clients that add a cache directive on the same path may prematurely uncache from each other.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5203
>                 URL: https://issues.apache.org/jira/browse/HDFS-5203
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS-4949
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: HDFS-4949
>
>         Attachments: HDFS-5203.1.patch, HDFS-5203.2.patch, HDFS-5203.3.patch
>
>
> When a client adds a cache directive, we assign it a unique ID and return that ID to the client.  If multiple clients add a cache directive for the same path, then we return the same ID.  If one client then removes the cache entry for that ID, then it is removed for all clients.  Then, when this change becomes visible in subsequent cache reports, the datanodes may {{munlock}} the block before the other clients are done with it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)