[
https://issues.apache.org/jira/browse/HDFS-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845756#comment-13845756
]
Andrew Wang commented on HDFS-5431:
-----------------------------------
The checkLimit flag makes sense to me, except I'd prefer "force", or if you'd
like it flipped, "enforce" or "strict". This is pretty easy.
I agree on synchronously waiting on the CRM in the listed scenarios, and a CV
would be a good way of doing this. It's a bit complicated though, since I don't
think we can get a FSN CV, especially with the new lock context in HDFS-5453
coming down the pipe I think kicking the CRM, releasing the FSN lock, waiting
on the CRM CV, then regetting the FSN lock should be okay, but it might be
simpler to just call into CRM directly to do the rescan.
I'll try the CV version, but if it looks too messy, we can go with a direct
call.
> 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
>
>
> We should support cachepool-based quota management in path-based caching.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
