Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 97217 invoked from network); 13 Feb 2007 19:01:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2007 19:01:00 -0000 Received: (qmail 47676 invoked by uid 500); 13 Feb 2007 19:01:06 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 47647 invoked by uid 500); 13 Feb 2007 19:01:06 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 47638 invoked by uid 99); 13 Feb 2007 19:01:06 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 11:01:06 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 11:00:58 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8DF2F7142CC for ; Tue, 13 Feb 2007 11:00:36 -0800 (PST) Message-ID: <5657596.1171393236578.JavaMail.jira@brutus> Date: Tue, 13 Feb 2007 11:00:36 -0800 (PST) From: "Raghu Angadi (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-973) NPE in FSDataset during heavy Namenode load In-Reply-To: <31103135.1170661445515.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472826 ] Raghu Angadi commented on HADOOP-973: ------------------------------------- I think we should have an explanation if this is expected. Currently it might be possible for namenode to ask to invalidate a block twice. This is not necessarily an error. In that case, not finding a file for a block might not be an exception but just a warning written to log. Also once we have a file for a block, there is no reason why 'volume' or 'parent' could be null. In that sense those conditions should not be handled as IOExceptions. > NPE in FSDataset during heavy Namenode load > ------------------------------------------- > > Key: HADOOP-973 > URL: https://issues.apache.org/jira/browse/HADOOP-973 > Project: Hadoop > Issue Type: Bug > Components: dfs > Affects Versions: 0.10.1, 0.11.0 > Reporter: Nigel Daley > Attachments: invalidDeletion.patch > > > Running namenode delete benchmark, I saw many of these NPE's traces in a datanode log: > ... > 2007-02-04 16:17:53,744 INFO org.apache.hadoop.dfs.DataNode: Deleting block blk_-949112377379974621 > 2007-02-04 16:17:53,744 INFO org.apache.hadoop.dfs.DataNode: Deleting block blk_748220495971269869 > 2007-02-04 16:17:54,619 INFO org.apache.hadoop.dfs.DataNode: Deleting block blk_658746956471887871 > 2007-02-04 16:17:56,752 ERROR org.apache.hadoop.dfs.DataNode: Exception: java.lang.NullPointerException > at org.apache.hadoop.dfs.FSDataset.invalidate(FSDataset.java:519) > at org.apache.hadoop.dfs.DataNode.offerService(DataNode.java:410) > at org.apache.hadoop.dfs.DataNode.run(DataNode.java:1033) > at java.lang.Thread.run(Thread.java:595) > 2007-02-04 16:18:01,754 INFO org.apache.hadoop.dfs.DataNode: using BLOCKREPORT_INTERVAL of 3329089msec > 2007-02-04 16:18:02,577 INFO org.apache.hadoop.dfs.DataNode: Deleting block blk_1657305102826276927 > 2007-02-04 16:18:02,577 INFO org.apache.hadoop.dfs.DataNode: Deleting block blk_589129256174830133 > ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.