Code review:
- You have a spurious newline in Server.doStop()
Other than that, it looks good.
On Mar 29, 2007, at 11:13 AM, dhruba borthakur (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1178?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1178:
-------------------------------------
Attachment: namenodestart.patch
Close listener socket connection. Also, interrupt all RPC server
handler threads.
NullPointer Exception in org.apache.hadoop.dfs.NameNode.isDir on
namenode restart
---------------------------------------------------------------------
------------
Key: HADOOP-1178
URL: https://issues.apache.org/jira/browse/
HADOOP-1178
Project: Hadoop
Issue Type: Bug
Components: dfs
Affects Versions: 0.13.0
Reporter: dhruba borthakur
Assigned To: dhruba borthakur
Fix For: 0.13.0
Attachments: namenodestart.patch
On a namenode restart, I sometimes get the following exception.
The problem is that the RPC server is initialized before the
namenode data structures are initialized. This means that an RPC
starts getting processed by the namenode before its data
structures are consistent. The fix is to first initialize the
namesystem and then start the RPC server.
NFO org.apache.hadoop.ipc.Server: IPC Server handler 1 on 50000
call error: java.io.IOException: java.lang.NullPointerException
java.io.IOException: java.lang.NullPointerException
at org.apache.hadoop.dfs.NameNode.isDir(NameNode.java:438)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
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:339)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:564)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
