hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8453) Erasure coding: properly handle start offset for internal blocks in a block group
Date Tue, 02 Jun 2015 23:16:50 GMT

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

Jing Zhao updated HDFS-8453:
----------------------------
       Resolution: Fixed
    Fix Version/s: HDFS-7285
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I've committed this. Thanks Zhe for the contribution and Walter for the review!

> Erasure coding: properly handle start offset for internal blocks in a block group
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-8453
>                 URL: https://issues.apache.org/jira/browse/HDFS-8453
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>             Fix For: HDFS-7285
>
>         Attachments: HDFS-8453-HDFS-7285.00.patch, HDFS-8453-HDFS-7285.01.patch
>
>
> {code}
>   void actualGetFromOneDataNode(final DNAddrPair datanode,
>     ...
>       LocatedBlock block = getBlockAt(blockStartOffset);
>     ...
>       fetchBlockAt(block.getStartOffset());
> {code}
> The {{blockStartOffset}} here is from inner block. For parity blocks, the offset will
overlap with the next block group, and we may end up with fetching wrong block. So we have
to assign a meaningful start offset for internal blocks in a block group, especially for parity
blocks.



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

Mime
View raw message