hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1831) BlockPlacement policy for RAID
Date Fri, 10 Dec 2010 22:31:04 GMT

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

dhruba borthakur updated MAPREDUCE-1831:

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks Scott!

> BlockPlacement policy for RAID
> ------------------------------
>                 Key: MAPREDUCE-1831
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1831
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/raid
>    Affects Versions: 0.23.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.23.0
>         Attachments: MAPREDUCE-1831-v2.txt, MAPREDUCE-1831.20100610.txt, MAPREDUCE-1831.txt,
MAPREDUCE-1831.v1.1.txt, test.result
> Raid introduce the new dependency between blocks within a file.
> The blocks help decode each other. Therefore we should avoid put them on the same machine.
> The proposed BlockPlacementPolicy does the following
> 1. When writing parity blocks, it avoid the parity blocks and source blocks sit together.
> 2. When reducing replication number, it deletes the blocks that sits with other dependent
> 3. It does not change the way we write normal files. It only has different behavior when
processing raid files.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message