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 "Andrew Wang (JIRA)" <ji...@apache.org> on 2013/03/01 04:51:15 UTC
[jira] [Assigned] (HDFS-3277) fail over to loading a different
FSImage if the first one we try to load is corrupt
[ https://issues.apache.org/jira/browse/HDFS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang reassigned HDFS-3277:
---------------------------------
Assignee: Andrew Wang (was: Colin Patrick McCabe)
> fail over to loading a different FSImage if the first one we try to load is corrupt
> -----------------------------------------------------------------------------------
>
> Key: HDFS-3277
> URL: https://issues.apache.org/jira/browse/HDFS-3277
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Colin Patrick McCabe
> Assignee: Andrew Wang
> Attachments: HDFS-3277.002.patch, HDFS-3277.003.patch, HDFS-3277.004.patch
>
>
> Most users store multiple copies of the FSImage in order to prevent catastrophic data loss if a hard disk fails. However, our image loading code is currently not set up to start reading another FSImage if loading the first one does not succeed. We should add this capability.
> We should also be sure to remove the FSImage directory that failed from the list of FSImage directories to write to, in the way we normally do when a write (as opopsed to read) fails.
--
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