You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jun Jin (JIRA)" <ji...@apache.org> on 2013/01/04 07:28:16 UTC
[jira] [Updated] (HDFS-4360) multiple BlockFixer should be
supported in order to improve scalability and reduce work on single
BlockFixer
[ https://issues.apache.org/jira/browse/HDFS-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Jin updated HDFS-4360:
--------------------------
Summary: multiple BlockFixer should be supported in order to improve scalability and reduce work on single BlockFixer (was: multiple BlockFixer should be supported in order to improve scalability and relief task on single BlockFixer)
> multiple BlockFixer should be supported in order to improve scalability and reduce work on single BlockFixer
> ------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4360
> URL: https://issues.apache.org/jira/browse/HDFS-4360
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: contrib/raid
> Affects Versions: 0.22.0
> Reporter: Jun Jin
> Labels: patch
>
> 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 RaidNode.java and RaidDFSUtil.getCorruptFile(), to enable fsck to check the different paths defined in separated Raid.xml for single RaidNode/BlockFixer
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira