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

Hudson commented on HDFS-2822:
------------------------------

Integrated in Hadoop-Common-0.23-Commit #404 (See 
[https://builds.apache.org/job/Hadoop-Common-0.23-Commit/404/])
    HDFS-2822. processMisReplicatedBlock incorrectly identifies 
under-construction blocks as under-replicated. Contributed by Todd Lipcon.

todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1234926
Files : 
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestSafeMode.java

                
> processMisReplicatedBlock incorrectly identifies under-construction blocks as 
> under-replicated
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-2822
>                 URL: https://issues.apache.org/jira/browse/HDFS-2822
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, name-node
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.24.0, 0.23.1
>
>         Attachments: hdfs-2822.txt
>
>
> When the NN processes mis-replicated blocks while exiting safemode, it 
> considers under-construction blocks as under-replicated, inserting them into 
> the neededReplicationsQueue. This makes them show up as corrupt in the 
> metrics and UI momentarily, until they're pulled off the queue. At that 
> point, it realizes that they aren't in fact under-replicated, correctly. This 
> affects both the HA branch and trunk/23, best I can tell.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to