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-4867) metaSave NPEs when there are invalid blocks in repl queue.
Date Wed, 05 Jun 2013 19:06:22 GMT

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

Hadoop QA commented on HDFS-4867:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12586365/HDFS-4867.branch2.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:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4483//console

This message is automatically generated.
                
> metaSave NPEs when there are invalid blocks in repl queue.
> ----------------------------------------------------------
>
>                 Key: HDFS-4867
>                 URL: https://issues.apache.org/jira/browse/HDFS-4867
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.4-alpha, 0.23.8
>            Reporter: Kihwal Lee
>            Assignee: Plamen Jeliazkov
>             Fix For: 3.0.0, 2.0.5-alpha
>
>         Attachments: HDFS-4867.branch-0.23.patch, HDFS-4867.branch2.patch, HDFS-4867.trunk.patch,
HDFS-4867.trunk.patch
>
>
> Since metaSave cannot get the inode holding a orphaned/invalid block, it NPEs and stops
generating further report. Normally ReplicationMonitor removes them quickly, but if the queue
is huge, it takes very long time. Also in safe mode, they stay.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message