hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5790) LeaseManager.findPath is very slow when many leases need recovery
Date Tue, 21 Jan 2014 23:48:21 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Todd Lipcon updated HDFS-5790:
------------------------------

    Attachment: hdfs-5790.txt

Attached patch gets rid of the slow method and just calls INode.getFullPathName() everywhere
it was used. My local test results above indicates this ought to work, and I don't see why
it wouldn't, but would appreciate some reviews.

> 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.4.0
>            Reporter: Todd Lipcon
>         Attachments: 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)

Mime
View raw message