hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5590) Block ID and generation stamp may be reused when persistBlocks is set to false
Date Fri, 06 Dec 2013 02:06:36 GMT

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

Hudson commented on HDFS-5590:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4844 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4844/])
HDFS-5590. Block ID and generation stamp may be reused when persistBlocks is set to false.
Contributed by Jing Zhao. (jing9: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1548368)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestPersistBlocks.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestBackupNode.java


> Block ID and generation stamp may be reused when persistBlocks is set to false
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-5590
>                 URL: https://issues.apache.org/jira/browse/HDFS-5590
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-5590.000.patch, HDFS-5590.001.patch
>
>
> In a cluster with non-HA setup and dfs.persist.blocks set to false, we may have data
loss in the following case:
> # client creates file1 and requests a block from NN and get blk_id1_gs1
> # client writes blk_id1_gs1 to DN
> # NN is restarted and because persistBlocks is false, blk_id1_gs1 may not be persisted
in disk
> # another client creates file2 and NN will allocate a new block using the same block
id blk_id1_gs1 since block ID and generation stamp are both increased sequentially.
> Now we may have two versions (file1 and file2) of the blk_id1_gs1 (same id, same gs)
in the system. It will case data loss.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message