[
https://issues.apache.org/jira/browse/HDFS-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680089#comment-14680089
]
Kihwal Lee edited comment on HDFS-8865 at 8/10/15 1:18 PM:
-----------------------------------------------------------
bq. Can we fix the quota by storage type update issue in a separate JIRA?
It is kind of hard to not do it, since that part of code is being modified. I
will just do whatever seems natural in the new code. We can make sure it is
fixed properly and improve the test case in HDFS-8879. We can set this jira as
a dependency of HDFS-8879, if it ends up containing the fix.
was (Author: kihwal):
bq. Can we fix the quota by storage type update issue in a separate JIRA?
It is kind of hard to not do it, since that part of code is being modified. I
will just do whatever seems natural in the new code. We can make sure it is
fixed properly and improve the test case in HDFS-8879.
> Improve quota initialization performance
> ----------------------------------------
>
> Key: HDFS-8865
> URL: https://issues.apache.org/jira/browse/HDFS-8865
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-8865.patch, HDFS-8865.v2.patch
>
>
> After replaying edits, the whole file system tree is recursively scanned in
> order to initialize the quota. For big name space, this can take a very long
> time. Since this is done during namenode failover, it also affects failover
> latency.
> By using the Fork-Join framework, I was able to greatly reduce the
> initialization time. The following is the test result using the fsimage from
> one of the big name nodes we have.
> || threads || seconds||
> | 1 (existing) | 55|
> | 1 (fork-join) | 68 |
> | 4 | 16 |
> | 8 | 8 |
> | 12 | 6 |
> | 16 | 5 |
> | 20 | 4 |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
