[ 
https://issues.apache.org/jira/browse/HDFS-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796220#comment-13796220
 ] 

Hadoop QA commented on HDFS-5346:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12608578/HDFS-5346.patch
  against trunk revision .

    {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}.  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.TestSafeMode
                  org.apache.hadoop.hdfs.server.namenode.TestAuditLogger

                                      The following test timeouts occurred in 
hadoop-hdfs-project/hadoop-hdfs:

org.apache.hadoop.hdfs.server.namenode.TestListCorruptFileBlocks

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/5203//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5203//console

This message is automatically generated.

> Replication queues should not be initialized in the middle of IBR processing.
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-5346
>                 URL: https://issues.apache.org/jira/browse/HDFS-5346
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, performance
>    Affects Versions: 0.23.9, 2.3.0
>            Reporter: Kihwal Lee
>            Assignee: Ravi Prakash
>             Fix For: 2.3.0, 0.23.10
>
>         Attachments: HDFS-5346.branch-23.patch, HDFS-5346.patch, 
> HDFS-5346.patch
>
>
> When initial block reports are being processed, checkMode() is called from 
> incrementSafeBlockCount(). This causes the replication queues to be 
> initialized in the middle of processing a block report in the IBR processing 
> mode. If there are many block reports waiting to be processed, 
> SafeModeMonitor won't be able to make name node leave the safe mode soon. It 
> appears that the block report processing speed degrades considerably during 
> this time. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to