[ 
https://issues.apache.org/jira/browse/HDFS-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289905#comment-15289905
 ] 

Hudson commented on HDFS-2173:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #9818 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9818/])
HDFS-2173. saveNamespace should not throw IOE when only one storage (wang: rev 
010e6ac328855bad59f138b6aeaec535272f448c)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestSaveNamespace.java


> 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
>            Assignee: Andras Bokor
>             Fix For: 2.9.0
>
>         Attachments: HDFS-2173.01.patch, HDFS-2173.02.patch, 
> HDFS-2173.02.patch, HDFS-2173.03.patch, HDFS-2173.04.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to