[
https://issues.apache.org/jira/browse/HDFS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602505#comment-13602505
]
Colin Patrick McCabe commented on HDFS-3277:
--------------------------------------------
bq. I agree about the secret manager, it looks like all the state being saved
is just reset later anyway. Removed that bit of code, but Colin can ring in if
we missed something.
ATM is correct that this code isn't needed now. Looking at the change history,
HDFS-3849 (which was done after I prepared the original patches for this JIRA)
added an {{FSNamesystem#clear}} method which made some of the stuff in the
original patches unnecessary.
Looks good to me.
> 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, HDFS-3277.005.patch, HDFS-3277.006.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
