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

Hudson commented on HDFS-7864:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2408 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2408/])
HDFS-7864. Erasure Coding: Update safemode calculation for striped (zhezhang: 
rev 46dac3595fa2e2c14290154c3c12ea799ee5043d)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/SafeMode.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockIdManager.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlocksMap.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestSafeMode.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java


> Erasure Coding: Update safemode calculation for striped blocks
> --------------------------------------------------------------
>
>                 Key: HDFS-7864
>                 URL: https://issues.apache.org/jira/browse/HDFS-7864
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: GAO Rui
>             Fix For: HDFS-7285
>
>         Attachments: HDFS-7864.1.patch, HDFS-7864.2.patch, HDFS-7864.3.patch, 
> HDFS-7864.4.patch
>
>
> We need to update the safemode calculation for striped blocks. Specifically, 
> each striped block now consists of multiple data/parity blocks stored in 
> corresponding DataNodes. The current code's calculation is thus inconsistent: 
> each striped block is only counted as 1 expected block, while each of its 
> member block may increase the number of received blocks by 1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to