hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8871) Decommissioning of a node with a failed volume may not start
Date Wed, 23 Sep 2015 23:24:04 GMT

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

Vinod Kumar Vavilapalli updated HDFS-8871:
------------------------------------------
              Labels:   (was: 2.6.1-candidate)
    Target Version/s: 2.7.2, 2.6.2

Dropping 2.6.1-candidate label, 2.6.1 is out now. Targetting 2.6.2 / 2.7.2.

> Decommissioning of a node with a failed volume may not start
> ------------------------------------------------------------
>
>                 Key: HDFS-8871
>                 URL: https://issues.apache.org/jira/browse/HDFS-8871
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Kihwal Lee
>            Assignee: Daryn Sharp
>            Priority: Critical
>
> Since staleness may not be properly cleared, a node with a failed volume may not actually
get scanned for block replication. Nothing is being replicated from these nodes.
> This bug does not manifest unless the datanode has a unique storage ID per volume. 



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

Mime
View raw message