hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramkumar Vadali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1819) RaidNode should be smarter in submitting Raid jobs
Date Wed, 29 Sep 2010 19:45:32 GMT

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

Ramkumar Vadali updated MAPREDUCE-1819:
---------------------------------------

    Attachment: MAPREDUCE-1819.patch.3

Addressed Scott's comments. The logic to decided if more files need to be selected for RAIDing
for a policy is now factored out into another function shouldSelectFiles()

> RaidNode should be smarter in submitting Raid jobs
> --------------------------------------------------
>
>                 Key: MAPREDUCE-1819
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1819
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: contrib/raid
>    Affects Versions: 0.20.1
>            Reporter: Ramkumar Vadali
>            Assignee: Ramkumar Vadali
>         Attachments: MAPREDUCE-1819.patch, MAPREDUCE-1819.patch.2, MAPREDUCE-1819.patch.3
>
>
> The RaidNode currently computes parity files as follows:
> 1. Using RaidNode.selectFiles() to figure out what files to raid for a policy
> 2. Using #1 repeatedly for each configured policy to accumulate a list of files. 
> 3. Submitting a mapreduce job with the list of files from #2 using DistRaid.doDistRaid()
> This task addresses the fact that #2 and #3 happen sequentially. The proposal is to submit
a separate mapreduce job for the list of files for each policy and use another thread to track
the progress of the submitted jobs. This will help reduce the time taken for files to be raided.

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


Mime
View raw message