Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 24 Jun 2016 22:25:16 +0000 (UTC)
From: "Kuhu Shukla (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12963568.1461863706000.25013.1466807116224@Atlassian.JIRA>
In-Reply-To: <JIRA.12963568.1461863706000@Atlassian.JIRA>
References: <JIRA.12963568.1461863706000@Atlassian.JIRA> <JIRA.12963568.1461863706802@arcas>
Subject: [jira] [Updated] (HDFS-10343) BlockManager#createLocatedBlocks may
 return blocks on failed storages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 24 Jun 2016 22:25:18 -0000


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

Kuhu Shukla updated HDFS-10343:
-------------------------------
    Attachment: HDFS-10343.001.patch

Attaching initial patch that removes failed storages and adjusts the machines array if needed.

> BlockManager#createLocatedBlocks may return blocks on failed storages
> ---------------------------------------------------------------------
>
>                 Key: HDFS-10343
>                 URL: https://issues.apache.org/jira/browse/HDFS-10343
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 2.6.0
>            Reporter: Daryn Sharp
>            Assignee: Kuhu Shukla
>         Attachments: HDFS-10343.001.patch
>
>
> Storage state is ignored when building the machines list.  Failed storage removal is not immediate so clients may be directed to bad locations.  The client recovers but it's less than ideal.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org