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 "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2015/08/05 21:31:06 UTC

[jira] [Commented] (HDFS-8486) DN startup may cause severe data loss

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

Xiaoyu Yao commented on HDFS-8486:
----------------------------------

Thanks Arpit. The branch-2.6 patch LGTM, +1.

> DN startup may cause severe data loss
> -------------------------------------
>
>                 Key: HDFS-8486
>                 URL: https://issues.apache.org/jira/browse/HDFS-8486
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 0.23.1, 2.0.0-alpha
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.1
>
>         Attachments: HDFS-8486-branch-2.6.02.patch, HDFS-8486-branch-2.6.patch, HDFS-8486.patch, HDFS-8486.patch
>
>
> A race condition between block pool initialization and the directory scanner may cause a mass deletion of blocks in multiple storages.
> If block pool initialization finds a block on disk that is already in the replica map, it deletes one of the blocks based on size, GS, etc.  Unfortunately it _always_ deletes one of the blocks even if identical, thus the replica map _must_ be empty when the pool is initialized.
> The directory scanner starts at a random time within its periodic interval (default 6h).  If the scanner starts very early it races to populate the replica map, causing the block pool init to erroneously delete blocks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)