[
https://issues.apache.org/jira/browse/HDFS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley updated HDFS-1955:
-----------------------------
Component/s: name-node
Description:
Prior to HDFS-1826, doUpgrade() would fail if any of the storage directories
failed to successfully write the new fsimage or edits files.
Now it appears to "succeed" even if some or all of the individual directories
fail.
There is some discussion about whether doUpgrade() should have some fault
tolerance, but for now make it fail on any single storage directory failure, as
before.
was:After HDFS-1071, saveNamespace now appears to "succeed" even if all of
the individual directories failed to save.
Priority: Major (was: Blocker)
Fix Version/s: (was: 0.22.0)
Assignee: Matt Foley (was: Aaron T. Myers)
Summary: HDFS-1826 made FSImage.doUpgrade() too fault-tolerant (was:
CLONE - saveNamespace appears to succeed even if all directories fail to save)
> HDFS-1826 made FSImage.doUpgrade() too fault-tolerant
> -----------------------------------------------------
>
> Key: HDFS-1955
> URL: https://issues.apache.org/jira/browse/HDFS-1955
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Matt Foley
> Assignee: Matt Foley
>
> Prior to HDFS-1826, doUpgrade() would fail if any of the storage directories
> failed to successfully write the new fsimage or edits files.
> Now it appears to "succeed" even if some or all of the individual directories
> fail.
> There is some discussion about whether doUpgrade() should have some fault
> tolerance, but for now make it fail on any single storage directory failure,
> as before.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
