You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:33:47 UTC

[jira] [Updated] (MAPREDUCE-4917) multiple BlockFixer should be supported in order to improve scalability and reduce too much work on single BlockFixer

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

Allen Wittenauer updated MAPREDUCE-4917:
----------------------------------------
    Labels: BB2015-05-TBR patch  (was: patch)

> multiple BlockFixer should be supported in order to improve scalability and reduce too much work on single BlockFixer
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4917
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4917
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/raid
>    Affects Versions: 0.22.0
>            Reporter: Jun Jin
>            Assignee: Jun Jin
>              Labels: BB2015-05-TBR, patch
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-4917.1.patch, MAPREDUCE-4917.2.patch
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> current implementation can only run single BlockFixer since the fsck (in RaidDFSUtil.getCorruptFiles) only check the whole DFS file system. multiple BlockFixer will do the same thing and try to fix same file if multiple BlockFixer launched.
> the change/fix will be mainly in BlockFixer.java and RaidDFSUtil.getCorruptFile(), to enable fsck to check the different paths defined in separated Raid.xml for single RaidNode/BlockFixer



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