Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 24238 invoked from network); 28 Nov 2006 00:32:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2006 00:32:58 -0000 Received: (qmail 40007 invoked by uid 500); 28 Nov 2006 00:33:07 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 39764 invoked by uid 500); 28 Nov 2006 00:33: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 39755 invoked by uid 99); 28 Nov 2006 00:33:06 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 16:33: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; Mon, 27 Nov 2006 16:32:56 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0F1697142E4 for ; Mon, 27 Nov 2006 16:32:21 -0800 (PST) Message-ID: <6752273.1164673941058.JavaMail.jira@brutus> Date: Mon, 27 Nov 2006 16:32:21 -0800 (PST) From: "Koji Noguchi (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-751) Namenode constantly using up 100% CPU MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Namenode constantly using up 100% CPU -------------------------------------- Key: HADOOP-751 URL: http://issues.apache.org/jira/browse/HADOOP-751 Project: Hadoop Issue Type: Bug Components: dfs Affects Versions: 0.8.0 Reporter: Koji Noguchi Trying to figure out the exact cause, but CPU load of the namenode is constantly 100% without any file exchanges. .log file of the namenode showing the following exception about every 20 seconds. 2006-11-27 16:02:07,199 INFO org.apache.hadoop.ipc.Server: IPC Server handler 5 on 8020 call error: java.io.IOException: java.util.NoSuchElementException java.io.IOException: java.util.NoSuchElementException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1029) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058) at java.util.AbstractCollection.toArray(AbstractCollection.java:176) at org.apache.hadoop.dfs.DatanodeDescriptor.getBlocks(DatanodeDescriptor.java:96) at org.apache.hadoop.dfs.FSNamesystem.processReport(FSNamesystem.java:1446) at org.apache.hadoop.dfs.NameNode.blockReport(NameNode.java:506) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:387) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:518) On some of the datanodes, .log file is showing 2006-11-27 16:03:57,542 WARN org.apache.hadoop.dfs.DataNode: org.apache.hadoop.ipc.RemoteException: java.io.IOException: java.util.NoSuchElementException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1029) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058) at java.util.AbstractCollection.toArray(AbstractCollection.java:176) at org.apache.hadoop.dfs.DatanodeDescriptor.getBlocks(DatanodeDescriptor.java:96) at org.apache.hadoop.dfs.FSNamesystem.processReport(FSNamesystem.java:1446) at org.apache.hadoop.dfs.NameNode.blockReport(NameNode.java:506) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:387) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:518) at org.apache.hadoop.ipc.Client$Connection.run(Client.java:248) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira