[
https://issues.apache.org/jira/browse/HDFS-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240653#comment-14240653
]
Hadoop QA commented on HDFS-7503:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12686171/HDFS-7503.trunk.02.patch
against trunk revision 2ed90a5.
{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:red}-1 findbugs{color}. The patch appears to introduce 40 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.blockmanagement.TestDatanodeManager
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8987//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/8987//artifact/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8987//console
This message is automatically generated.
> Namenode restart after large deletions can cause slow processReport (due to
> logging)
> ------------------------------------------------------------------------------------
>
> Key: HDFS-7503
> URL: https://issues.apache.org/jira/browse/HDFS-7503
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 1.2.1, 2.6.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HDFS-7503.branch-1.patch, HDFS-7503.trunk.01.patch,
> HDFS-7503.trunk.02.patch
>
>
> If a large directory is deleted and namenode is immediately restarted, there
> are a lot of blocks that do not belong to any file. This results in a log:
> {code}
> 2014-11-08 03:11:45,584 INFO BlockStateChange
> (BlockManager.java:processReport(1901)) - BLOCK* processReport:
> blk_1074250282_509532 on 172.31.44.17:1019 size 6 does not belong to any file.
> {code}
> This log is printed within FSNamsystem lock. This can cause namenode to take
> long time in coming out of safemode.
> One solution is to downgrade the logging level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
