[
https://issues.apache.org/jira/browse/HDFS-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032781#comment-13032781
]
Matt Foley commented on HDFS-1505:
----------------------------------
bq. ...failure handling should perhaps be different between these two cases
[saveNamespace and doUpgrade]
The inclination of our team is leave the behavior unchanged here, and open
another Jira for that discussion.
Historical info:
* A quick review of the patches for HDFS-1071 and HDFS-1826 indicates that
prior to making FSImage write concurrent, saveNamespace logged storage
directory failures and continued, but doUpgrade killed the Namenode on any
failure.
* With the concurrent write code, both now log and continue. This may be a
deficiency in my HDFS-1826 patch.
* HDFS-4885 introduced the ability to recover from transient storage dir
failures.
> saveNamespace appears to succeed even if all directories fail to save
> ---------------------------------------------------------------------
>
> Key: HDFS-1505
> URL: https://issues.apache.org/jira/browse/HDFS-1505
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Assignee: Aaron T. Myers
> Priority: Blocker
> Fix For: 0.22.0
>
> Attachments: hdfs-1505-1-test.txt, hdfs-1505-22.0.patch,
> hdfs-1505-22.1.patch, hdfs-1505-test.txt, hdfs-1505-trunk.0.patch,
> hdfs-1505-trunk.1.patch
>
>
> After HDFS-1071, saveNamespace now appears to "succeed" even if all of the
> individual directories failed to save.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
