Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9BFC418DB1 for ; Thu, 25 Jun 2015 22:24:05 +0000 (UTC) Received: (qmail 95367 invoked by uid 500); 25 Jun 2015 22:24:05 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 95280 invoked by uid 500); 25 Jun 2015 22:24:05 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 94981 invoked by uid 99); 25 Jun 2015 22:24:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2015 22:24:05 +0000 Date: Thu, 25 Jun 2015 22:24:05 +0000 (UTC) From: "Jing Zhao (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-8669) Erasure Coding: handle missing internal block locations in DFSStripedInputStream MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-8669: ---------------------------- Description: Currently DFSStripedInputStream assumes we always have complete internal block location information, i.e., we can always get all the DataNodes for a striped block group. In a lot of scenarios the client cannot get complete block location info, e.g., some internal blocks are missing and the NameNode has not finished the recovery yet. We should add functionality to handle missing block locations in DFSStripedInputStream. (was: Currently DFSStripedInputStream assumes we always have complete internal block location information, i.e., we can always get all the DataNodes for a striped block group. We should add functionality to handle missing block locations.) > Erasure Coding: handle missing internal block locations in DFSStripedInputStream > -------------------------------------------------------------------------------- > > Key: HDFS-8669 > URL: https://issues.apache.org/jira/browse/HDFS-8669 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Jing Zhao > Assignee: Jing Zhao > > Currently DFSStripedInputStream assumes we always have complete internal block location information, i.e., we can always get all the DataNodes for a striped block group. In a lot of scenarios the client cannot get complete block location info, e.g., some internal blocks are missing and the NameNode has not finished the recovery yet. We should add functionality to handle missing block locations in DFSStripedInputStream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)