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] [Commented] (HDFS-8871) Decommissioning of a node with a failed volume may not start
Date Mon, 04 Apr 2016 20:31:26 GMT

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

Vinod Kumar Vavilapalli commented on HDFS-8871:
-----------------------------------------------

[~daryn] / [~kihwal], any update on this? Is this still a bug? Considering this for a 2.7.3
RC later this week. Thanks.


> 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