Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 26006 invoked from network); 16 Jul 2007 18:53:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Jul 2007 18:53:26 -0000 Received: (qmail 54558 invoked by uid 500); 16 Jul 2007 18:53:28 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 54384 invoked by uid 500); 16 Jul 2007 18:53:27 -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 54369 invoked by uid 99); 16 Jul 2007 18:53:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jul 2007 11:53:27 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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, 16 Jul 2007 11:53:24 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9BBFE714191 for ; Mon, 16 Jul 2007 11:53:04 -0700 (PDT) Message-ID: <22438803.1184611984634.JavaMail.jira@brutus> Date: Mon, 16 Jul 2007 11:53:04 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-1541) ipc.Server INFO message shouldn't include an Exception trace In-Reply-To: <11529442.1183003165904.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-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512998 ] dhruba borthakur commented on HADOOP-1541: ------------------------------------------ I think it is natural for getFileInfo() to throw an exception if the file is not found (instead of returning null). I would hate to go back to a C-style coding form (and check for null everywhere getFileInfo is called) just to accomodate a certain logging behavour in the server logs. The reason it is a blocker is that exceptions in the namenode logs makes a cluster administrator jittery and results in lots of questions. > ipc.Server INFO message shouldn't include an Exception trace > ------------------------------------------------------------ > > Key: HADOOP-1541 > URL: https://issues.apache.org/jira/browse/HADOOP-1541 > Project: Hadoop > Issue Type: Bug > Components: dfs > Affects Versions: 0.14.0 > Reporter: Nigel Daley > Assignee: dhruba borthakur > Priority: Blocker > Fix For: 0.14.0 > > Attachments: ipcExceptionLog2.patch > > > I see a lot of these in the NN log. I don't think an INFO message should contain an error message and stack trace. > 2007-06-28 00:21:51,057 INFO org.apache.hadoop.ipc.Server: IPC Server handler 7 on 8020, call getFileInfo(/user/hadoopqa/mapred.loadtest/intermediateouts) from 2.2.2.2:47476: error: java.io.IOException: File does not exist > java.io.IOException: File does not exist > at org.apache.hadoop.dfs.FSDirectory.getFileInfo(FSDirectory.java:716) > at org.apache.hadoop.dfs.FSNamesystem.getFileInfo(FSNamesystem.java:1178) > at org.apache.hadoop.dfs.NameNode.getFileInfo(NameNode.java:479) > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.