[
https://issues.apache.org/jira/browse/HDFS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497789#comment-13497789
]
Hadoop QA commented on HDFS-4186:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553607/hdfs-4186-trunk-skip-standbyException.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestHDFSFileSystemContract
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3512//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3512//console
This message is automatically generated.
> 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: 0.23.4, 2.0.2-alpha
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Attachments:
> hdfs-4186-branch-0.23-inaccurate-batched-sync-count.patch,
> hdfs-4186-trunk.patch, hdfs-4186-trunk-skip-standbyException.patch
>
>
> 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
