hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8871) Decommissioning of a node with a failed volume may not start
Date Thu, 06 Aug 2015 22:10:04 GMT

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

Kihwal Lee commented on HDFS-8871:
----------------------------------

A patch written by [~daryn] has been tested. It is not clear whether the re-written decomm
manager is immune to this. I will let  [~daryn] post the patch for 2.6 and decide what to
do about 2.7 and beyond.

> 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
>              Labels: 2.6.1-candidate
>
> 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