hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7503) Namenode restart after large deletions can cause slow processReport (due to logging)
Date Wed, 10 Dec 2014 00:10:12 GMT

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

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/12686132/HDFS-7503.trunk.01.patch
  against trunk revision 03867eb.

    {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:red}-1 javac{color}.  The applied patch generated 1247 javac compiler warnings
(more than the trunk's current 1215 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 following test timeouts occurred in hadoop-hdfs-project/hadoop-hdfs-nfs:

org.apache.hadoop.hdfs.nfs.TTests
org.apache.hadoop.hdfs.nfs.nfs3.TeTests
org.apache.hadoop.hdfs.nfs.nfs3.TestClientAccessTests
org.apache.hadoop.hdfs.nfs.nfs3.TestNfs3HTests
org.apache.hadoop.hdfs.nfs.nfs3.TestRpcPrTests
org.apache.hadoop.hdfs.nfs.nfs3.TTests
org.apache.hadoop.hdfs.nfs.nfs3.TestOpenFilTests

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8983//testReport/
Javac warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/8983//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8983//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
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message