hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8486) DN startup may cause severe data loss
Date Tue, 18 Aug 2015 22:23:47 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arpit Agarwal updated HDFS-8486:
--------------------------------
    Attachment: HDFS-8486-branch-2.6.addendum.patch

Addendum patch to fix an issue introduced by conflict resolution with HDFS-7430.

> 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.6.1, 2.7.1
>
>         Attachments: HDFS-8486-branch-2.6.02.patch, HDFS-8486-branch-2.6.addendum.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)

Mime
View raw message