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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/07/20 02:39:57 UTC
[jira] [Created] (HDFS-2173) saveNamespace should not throw IOE
when only one storage directory fails to write VERSION file
saveNamespace should not throw IOE when only one storage directory fails to write VERSION file
----------------------------------------------------------------------------------------------
Key: HDFS-2173
URL: https://issues.apache.org/jira/browse/HDFS-2173
Project: Hadoop HDFS
Issue Type: Sub-task
Affects Versions: Edit log branch (HDFS-1073), 0.23.0
Reporter: Todd Lipcon
This JIRA tracks a TODO in TestSaveNamespace. Currently, if, while writing the VERSION files in the storage directories, one of the directories fails, the entire operation throws IOE. This is unnecessary -- instead, just that directory should be marked as failed.
This is targeted to be fixed _after_ HDFS-1073 is merged to trunk, since it does not ever dataloss, and would rarely occur in practice (the dir would have to fail between writing the fsimage file and writing VERSION)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2173) saveNamespace should not throw IOE
when only one storage directory fails to write VERSION file
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068565#comment-13068565 ]
Todd Lipcon commented on HDFS-2173:
-----------------------------------
I made it a subtask since the bug is in code which has been mostly rewritten in the branch. So, if it got fixed in trunk before 1073 was merged, we'd just have to re-fix it.
> saveNamespace should not throw IOE when only one storage directory fails to write VERSION file
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-2173
> URL: https://issues.apache.org/jira/browse/HDFS-2173
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: Edit log branch (HDFS-1073), 0.23.0
> Reporter: Todd Lipcon
> Fix For: 0.23.0
>
>
> This JIRA tracks a TODO in TestSaveNamespace. Currently, if, while writing the VERSION files in the storage directories, one of the directories fails, the entire operation throws IOE. This is unnecessary -- instead, just that directory should be marked as failed.
> This is targeted to be fixed _after_ HDFS-1073 is merged to trunk, since it does not ever dataloss, and would rarely occur in practice (the dir would have to fail between writing the fsimage file and writing VERSION)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2173) saveNamespace should not throw IOE
when only one storage directory fails to write VERSION file
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068559#comment-13068559 ]
Eli Collins commented on HDFS-2173:
-----------------------------------
Should this be a separate issue? It's not related to 1073 right?
> saveNamespace should not throw IOE when only one storage directory fails to write VERSION file
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-2173
> URL: https://issues.apache.org/jira/browse/HDFS-2173
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: Edit log branch (HDFS-1073), 0.23.0
> Reporter: Todd Lipcon
> Fix For: 0.23.0
>
>
> This JIRA tracks a TODO in TestSaveNamespace. Currently, if, while writing the VERSION files in the storage directories, one of the directories fails, the entire operation throws IOE. This is unnecessary -- instead, just that directory should be marked as failed.
> This is targeted to be fixed _after_ HDFS-1073 is merged to trunk, since it does not ever dataloss, and would rarely occur in practice (the dir would have to fail between writing the fsimage file and writing VERSION)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira