[
https://issues.apache.org/jira/browse/HDFS-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799486#comment-13799486
]
Chris Nauroth commented on HDFS-5203:
-------------------------------------
I also meant to mention that I discovered a bug in the path filtering
introduced by the conversion to {{Path}} objects in HDFS-5224. It was trying
to run {{#equals}} between a {{String}} and a {{Path}}, which of course is
always false. I'm planning on rolling a one-liner fix into this patch.
{code}
if (filterPath != null &&
- !directive.getPath().equals(filterPath)) {
+ !directive.getPath().toUri().getPath().equals(filterPath)) {
continue;
{code}
> 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: Bug
> Components: namenode
> Affects Versions: HDFS-4949
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-5203.1.patch, HDFS-5203.2.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)
