[
https://issues.apache.org/jira/browse/HDFS-7603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279733#comment-14279733
]
Hadoop QA commented on HDFS-7603:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12692626/HDFS-7603.patch
against trunk revision 780a6bf.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc 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 2.0.3) 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.server.namenode.TestFileTruncate
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9231//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9231//console
This message is automatically generated.
> The background replication queue initialization may not let others run
> ----------------------------------------------------------------------
>
> Key: HDFS-7603
> URL: https://issues.apache.org/jira/browse/HDFS-7603
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: rolling upgrades
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Critical
> Attachments: HDFS-7603.patch, HDFS-7603.patch
>
>
> The background replication queue initialization processes configured number
> of blocks at a time and releases the namesystem write lock. This was to let
> namenode start serving right after a standby to active transition or leaving
> safe mode. However, this does not allow others to run much if the lock
> fairness is set to "unfair" for the higher throughput.
> I propose adding a delay between unlocking and locking in the async repl
> queue init thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
