hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-4186) logSync() is called with the write lock held while releasing lease
Date Wed, 14 Nov 2012 02:32:13 GMT
Kihwal Lee created HDFS-4186:
--------------------------------

             Summary: logSync() is called with the write lock held while releasing lease
                 Key: HDFS-4186
                 URL: https://issues.apache.org/jira/browse/HDFS-4186
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: name-node
    Affects Versions: 2.0.2-alpha, 0.23.4
            Reporter: Kihwal Lee
            Priority: Critical


As pointed out in HDFS-4138, when the lease monitor calls internalReleaseLease(), it acquires
the namespace write lock. Inside internalReleaseLease(), if a block recovery is needed, the
lease is reassigned to the namenode itself and this is logged & synced in logReassignLease().

Since this is done while the write lock is held, log syncing is blocked. When a large number
of leases are expired and blocks are recovered, namenode can slow down.

--
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

Mime
View raw message