Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9D8410DB8 for ; Wed, 19 Mar 2014 23:07:52 +0000 (UTC) Received: (qmail 10950 invoked by uid 500); 19 Mar 2014 23:07:46 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 10775 invoked by uid 500); 19 Mar 2014 23:07:44 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 10747 invoked by uid 99); 19 Mar 2014 23:07:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2014 23:07:43 +0000 Date: Wed, 19 Mar 2014 23:07:43 +0000 (UTC) From: "Tsz Wo Nicholas Sze (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HDFS-2282) Semi-harmless race between block reports and block invalidation 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-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze resolved HDFS-2282. --------------------------------------- Resolution: Not A Problem I believe this is "Not A Problem" anymore. Please feel free to reopen it if it is not the case. > Semi-harmless race between block reports and block invalidation > --------------------------------------------------------------- > > Key: HDFS-2282 > URL: https://issues.apache.org/jira/browse/HDFS-2282 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode > Affects Versions: 0.20.203.0, 0.24.0 > Reporter: Todd Lipcon > Attachments: hdfs-2282-20.txt, hdfs-2282-20.txt > > > In the 0.20.203 codebase, block reports are not synchronized in any way against mutations to the actual file structure on disk. If a file is removed from a directory while the block report is scanning that directory, it will be mistakenly reported as existing with a length of 0, since File.length() on a non-existent file returns 0. > This results in an error being logged on the DataNode when the NN sends it a second block deletion request for the already-deleted block. I believe it to be harmless, but the error message can concern users. > This was fixed in the 0.20 code line in HDFS-2379. This jira remains open to track the port to 0.24. -- This message was sent by Atlassian JIRA (v6.2#6252)