hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hui Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7994) Detect if resevered EC Block ID is already used
Date Thu, 16 Apr 2015 08:08:58 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Hui Zheng updated HDFS-7994:
    Attachment: HDFS-7994_002.patch

Thanks [~szetszwo] for reviewing!
Consider we are using BlockManager to manage hasNonEcBlockUsingStripID,I added a method "addBlockCollectionWithCheck"
which do some additional check and update the hasNonEcBlockUsingStripID and reuse "addBlockCollection"
 into BlockManager.

> Detect if resevered EC Block ID is already used
> -----------------------------------------------
>                 Key: HDFS-7994
>                 URL: https://issues.apache.org/jira/browse/HDFS-7994
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Hui Zheng
>         Attachments: HDFS-7994_001.patch, HDFS-7994_002.patch
> Since random block IDs were supported by some early version of HDFS, the block ID reserved
for EC blocks could be already used by some existing blocks in a cluster. During NameNode
startup, it detects if there are reserved EC block IDs used by non-EC blocks. If it is the
case, NameNode will do an additional blocksMap lookup when there is a miss in a blockGroupsMap

This message was sent by Atlassian JIRA

View raw message