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-1348) Improve NameNode reponsiveness while it is checking if datanode decommissions are complete
Date Sat, 19 Feb 2011 15:32:38 GMT

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

Hadoop QA commented on HDFS-1348:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12455885/decomissionImp2.patch
  against trunk revision 1072023.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  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.

    -1 patch.  The patch command could not apply the patch.

Console output: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/189//console

This message is automatically generated.

> Improve NameNode reponsiveness while it is checking if datanode decommissions are complete
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1348
>                 URL: https://issues.apache.org/jira/browse/HDFS-1348
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>         Attachments: decomissionImp1.patch, decomissionImp2.patch, decommission.patch,
decommission1.patch
>
>
> NameNode normally is busy all the time. Its log is full of activities every second. But
once for a while, NameNode seems to pause for more than 10 seconds without doing anything,
leaving a blank in its log even though no garbage collection is happening.  All other requests
to NameNode are blocked when this is happening.
> One culprit is DecommionManager. Its monitor holds the fsynamesystem lock during the
whole process of checking if decomissioning DataNodes are finished or not, during which it
checks every block of up to a default of 5 datanodes.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message