Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 65098 invoked from network); 14 Aug 2009 13:37:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Aug 2009 13:37:30 -0000 Received: (qmail 91453 invoked by uid 500); 14 Aug 2009 13:37:37 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 91397 invoked by uid 500); 14 Aug 2009 13:37:37 -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 91380 invoked by uid 99); 14 Aug 2009 13:37:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 13:37:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 13:37:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CD9E3234C004 for ; Fri, 14 Aug 2009 06:37:14 -0700 (PDT) Message-ID: <1331877688.1250257034828.JavaMail.jira@brutus> Date: Fri, 14 Aug 2009 06:37:14 -0700 (PDT) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-532) Allow applications to know that a read request failed because block is missing In-Reply-To: <1061306482.1249587195243.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743196#action_12743196 ] Hudson commented on HDFS-532: ----------------------------- Integrated in Hadoop-Hdfs-trunk #49 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk/49/]) . Allow applications to know that a read request failed because block is missing. (dhruba) > Allow applications to know that a read request failed because block is missing > ------------------------------------------------------------------------------ > > Key: HDFS-532 > URL: https://issues.apache.org/jira/browse/HDFS-532 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs client > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Fix For: 0.21.0 > > Attachments: BlockMissingException.patch, BlockMissingException2.txt > > > I have an application that has intelligence to retrieve data from alternate locations if HDFS cannot provide this data. This can happen when data in HDFS is corrupted or the block is missing. HDFS already throws ChecksumException if the block is corrupted and throws a generic IOException if the block is missing. I would like HDFS to throw BlockMissingException when a read request encounters a block that has no locations associated with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.