Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 4 Mar 2013 18:39:12 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12635068.1362370905603.376637.1362422352831@arcas>
In-Reply-To: <JIRA.12635068.1362370905603@arcas>
References: <JIRA.12635068.1362370905603@arcas>
Subject: [jira] [Commented] (HDFS-4544) Error in deleting blocks should not
 do check disk, for all types of errors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-4544:
---------------------------------------

+1. This seems like a good change.
                
> Error in deleting blocks should not do check disk, for all types of errors
> --------------------------------------------------------------------------
>
>                 Key: HDFS-4544
>                 URL: https://issues.apache.org/jira/browse/HDFS-4544
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Amareshwari Sriramadasu
>             Fix For: 1.2.0
>
>
> The following code in Datanode.java 
> {noformat}
>       try {
>         if (blockScanner != null) {
>           blockScanner.deleteBlocks(toDelete);
>         }
>         data.invalidate(toDelete);
>       } catch(IOException e) {
>         checkDiskError();
>         throw e;
>       }
> {noformat}
> causes check disk to happen in case of any errors during invalidate.
> We have seen errors like :
> 2013-03-02 00:08:28,849 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Unexpected error trying to delete block blk_-2973118207682441648_225738165. BlockInfo not found in volumeMap.
> And all such errors trigger check disk, making the clients timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira