[
https://issues.apache.org/jira/browse/HDFS-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326648#comment-14326648
]
Jing Zhao commented on HDFS-7723:
---------------------------------
I just noticed that {{INodeFile#computeQuotaUsage}} calls
{{getStoragePolicyID}} to identify the storage policy id of the file. This may
not be very efficient (especially when we're computing the quota usage of a
directory) because {{getStoragePolicyID}} may recursively check the ancestral
INode's storage policy. I think here an improvement can be passing the lowest
parent directory's storage policy down while traversing the tree. What do you
think, [~xyao] and [~arpitagarwal]?
> Quota By Storage Type namenode implemenation
> --------------------------------------------
>
> Key: HDFS-7723
> URL: https://issues.apache.org/jira/browse/HDFS-7723
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Fix For: 2.7.0
>
> Attachments: HDFS-7723.0.patch, HDFS-7723.1.patch, HDFS-7723.2.patch,
> HDFS-7723.3.patch, HDFS-7723.4.patch, HDFS-7723.5.patch, HDFS-7723.6.patch,
> editsStored
>
>
> This includes: 1) new editlog to persist quota by storage type op 2)
> corresponding fsimage load/save the new op. 3) QuotaCount refactor to update
> usage of the storage types for quota enforcement 4) Snapshot support 5) Unit
> test update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
