[
https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-5431:
------------------------------
Attachment: hdfs-5431-4.patch
Hi Colin, I made the suggested changes with the following notes:
* With the new EnumSet, I also added a version of add/modify directive without
a {{flags}} argument, since it's really annoying to put
{{EnumSet.noneOf(CacheFlag.class}} everywhere.
* I don't like putting {{bytesOverlimit}} in {{CachePoolEntry}} because it
feels inconsistent with {{CachePoolStats}}. Left it as is, unless you feel
strongly on this one.
* Tweaked the kick behavior somewhat. We now try to do read-after-write
consistency with the dirty bit. add/modify with force is essentially a read and
a write.
This also does complete the test refactor, so we can close that other JIRA out
after this one goes in.
> support cachepool-based limit management in path-based caching
> --------------------------------------------------------------
>
> Key: HDFS-5431
> URL: https://issues.apache.org/jira/browse/HDFS-5431
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Affects Versions: 3.0.0
> Reporter: Colin Patrick McCabe
> Assignee: Andrew Wang
> Attachments: hdfs-5431-1.patch, hdfs-5431-2.patch, hdfs-5431-3.patch,
> hdfs-5431-4.patch
>
>
> We should support cachepool-based limit management in path-based caching.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
