[
https://issues.apache.org/jira/browse/HADOOP-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465839
]
Raghu Angadi commented on HADOOP-898:
-------------------------------------
Regd 898-post-803-revert.patch Nigel Daley wrote:
> Rather than apply a patch that effectively reverts HADOOP-803, it would
> be better to revert the patch using svn and then apply the neccessary
> (one line) patch to re-introduce the change needed by the overlapping
> HADOOP-855 patch. The svn command that I've applied and tested is:
>
> svn merge -r 496845:496844 .
>
> (where . is my trunk directory)
>
> I will also attach the one line diff that was necessary to apply after
> the above merge command.
> namenode generates infinite stream of null pointers
> ---------------------------------------------------
>
> Key: HADOOP-898
> URL: https://issues.apache.org/jira/browse/HADOOP-898
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: Owen O'Malley
> Assigned To: Raghu Angadi
> Attachments: 898-post-803-revert.patch, HADOOP-898-2.patch,
> HADOOP-898.patch
>
>
> My namenode is generating a constant stream of NullPointerExceptions. The log
> looks like:
> 2007-01-17 19:51:27,461 INFO org.apache.hadoop.ipc.Server: IPC Server handler
> 3
> on 50000 call error: java.io.IOException: java.lang.NullPointerException
> java.io.IOException: java.lang.NullPointerException
> at
> org.apache.hadoop.dfs.FSNamesystem.addStoredBlock(FSNamesystem.java:1621)
> at
> org.apache.hadoop.dfs.FSNamesystem.processReport(FSNamesystem.java:1563)
> at org.apache.hadoop.dfs.NameNode.blockReport(NameNode.java:573)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:589)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:337)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:538)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
