[
https://issues.apache.org/jira/browse/HDFS-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887746#comment-13887746
]
Hudson commented on HDFS-5790:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1659 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1659/])
HDFS-5790. LeaseManager.findPath is very slow when many leases need recovery.
Contributed by Todd Lipcon. (todd:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1562970)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/LeaseManager.java
> LeaseManager.findPath is very slow when many leases need recovery
> -----------------------------------------------------------------
>
> Key: HDFS-5790
> URL: https://issues.apache.org/jira/browse/HDFS-5790
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode, performance
> Affects Versions: 2.3.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 3.0.0, 2.4.0
>
> Attachments: hdfs-5790.txt, hdfs-5790.txt
>
>
> We recently saw an issue where the NN restarted while tens of thousands of
> files were open. The NN then ended up spending multiple seconds for each
> commitBlockSynchronization() call, spending most of its time inside
> LeaseManager.findPath(). findPath currently works by looping over all files
> held for a given writer, and traversing the filesystem for each one. This
> takes way too long when tens of thousands of files are open by a single
> writer.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
