[
https://issues.apache.org/jira/browse/HDFS-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709081#comment-13709081
]
Suresh Srinivas commented on HDFS-4995:
---------------------------------------
bq. We've seen it taking over 20 seconds.
How big was the directory? That seems like an awful lot of time.
bq. Lock directory when obtaining a copy of children list (ReadOnlyList).
I am not sure what you are proposing. Are you saying you will make a read only
copy of the children list of the directory for which content summary is being
computed? What happens to the lock if the parent directory is deleted?
> Make getContentSummary() less expensive
> ---------------------------------------
>
> Key: HDFS-4995
> URL: https://issues.apache.org/jira/browse/HDFS-4995
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.9, 2.3.0
> Reporter: Kihwal Lee
>
> When users call du or count DFS command, getContentSummary() method is called
> against namenode. If the directory has many directories and files, it could
> hold the namesystem lock for a long time. We've seen it taking over 20
> seconds. Namenode should not allow regular users to cause extended locking.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
