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-6186) Pause deletion of blocks when the namenode starts up
Date Tue, 13 May 2014 08:42:18 GMT

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

Hadoop QA commented on HDFS-6186:
---------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {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: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:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.

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

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

This message is automatically generated.

> Pause deletion of blocks when the namenode starts up
> ----------------------------------------------------
>
>                 Key: HDFS-6186
>                 URL: https://issues.apache.org/jira/browse/HDFS-6186
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Jing Zhao
>         Attachments: HDFS-6186.000.patch, HDFS-6186.002.patch, HDFS-6186.003.patch
>
>
> HDFS namenode can delete blocks very quickly, given the deletion happens as a parallel
operation spread across many datanodes. One of the frequent anxieties I see is that a lot
of data can be deleted very quickly, when a cluster is brought up, especially when one of
the storage directories has failed and namenode metadata was copied from another storage.
Copying wrong metadata would results in some of the newer files (if old metadata was copied)
being deleted along with their blocks. 
> HDFS-5986 now captures the number of pending deletion block on namenode webUI and JMX.
I propose pausing deletion of blocks for a configured period of time (default 1 hour?) after
namenode comes out of safemode. This will give enough time for the administrator to notice
large number of pending deletion blocks and take corrective action.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message