[
https://issues.apache.org/jira/browse/HADOOP-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513948
]
dhruba borthakur commented on HADOOP-1541:
------------------------------------------
With the coming of the block level CRC, the delete-if-exists code in the
ChecksumFileSystem is not invoked in the regular code path at all. So, this
problem has gone away.
A nightly benchmark run with the old code caused about 200 of these exceptions
in the namenode log. With the current trunk, i do not see a single exception in
the namenode log. I am inclined to mark this as 'resolved', or at least move it
off the "Blocker" queue. Does it sound reasonable?
> 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: ipcExceptionLog3.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.
