[
https://issues.apache.org/jira/browse/HDFS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310186#comment-14310186
]
Hadoop QA commented on HDFS-1348:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12455885/decomissionImp2.patch
against trunk revision da2fb2b.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9473//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: namenode
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
