|
|
| Created: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
 
United States |
2007-03-28 16:39:25 |
NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
------------------------------------------------------------
---------------------
Key: HADOOP-1178
URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1178
Project: Hadoop
Issue Type: Bug
Components: dfs
Reporter: dhruba borthakur
Fix For: 0.12.2
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(NativeMethodAcce
ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Assigned: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
name |
United States |
2007-03-28 16:39:25 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur reassigned HADOOP-1178:
----------------------------------------
Assignee: dhruba borthakur
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1178
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assigned To: dhruba borthakur
> Fix For: 0.12.2
>
>
> 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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-28 18:34:26 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1178:
-------------------------------------
Attachment: namenodestart.patch
Start the namenode RPC server only after the namesystem is
configured.
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1178
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assigned To: dhruba borthakur
> Fix For: 0.12.2
>
> 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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Commented: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
nam |
United States |
2007-03-28 19:35:25 |
[ https://issues.apache.org/jira/browse
/HADOOP-1178?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12485040 ]
Konstantin Shvachko commented on HADOOP-1178:
---------------------------------------------
I have the same problem. The order of starting RPC and
constructing FSNamespace() was changed by HADOOP-1085.
For me it appears a little different, when I restart the
name-node in the same process after it failed to start first
time.
Even with this patch I see
Address already in use
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:119)
at
sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java
:59)
at
org.apache.hadoop.ipc.Server$Listener.<init>(Server.ja
va:185)
at
org.apache.hadoop.ipc.Server.<init>(Server.java:626)
at
org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
at
org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
at
org.apache.hadoop.dfs.NameNode.init(NameNode.java:164)
at
org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:20
5)
at
org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:
820)
at
org.apache.hadoop.dfs.UpgradeUtilities.startCluster(UpgradeU
tilities.java:144)
at
org.apache.hadoop.dfs.TestDFSUpgrade.testUpgrade(TestDFSUpgr
ade.java:157)
This means the socket has not been closed properly.
I think that hadoop.ipc.Server.Listener.doStop() should
close the socket:
acceptChannel.socket().close()
We can also interrupt the Listener thread in Server.stop()
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1178
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assigned To: dhruba borthakur
> Fix For: 0.12.2
>
> 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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Commented: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
nam |
United States |
2007-03-28 22:32:25 |
[ https://issues.apache.org/jira/browse
/HADOOP-1178?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12485058 ]
Arun C Murthy commented on HADOOP-1178:
---------------------------------------
As Konstantin pointed out this is an artefact of HADOOP-1085
...
+1
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1178
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assigned To: dhruba borthakur
> Fix For: 0.12.2
>
> 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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-29 12:41:25 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-1178:
--------------------------------
Fix Version/s: (was: 0.12.2)
0.13.0
Affects Version/s: 0.13.0
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-29 13:11:25 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1178:
-------------------------------------
Attachment: (was: namenodestart.patch)
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://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
>
>
> 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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-29 13:13:25 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.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: htt
ps://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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-29 13:39:27 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1178:
-------------------------------------
Attachment: namenodestart2.patch
This removes a unnecessary newline introduced by the last
patch. Thanks Nigel for pointing it out.
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://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,
namenodestart2.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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|
| Updated: (HADOOP-1178) NullPointer
Exception in
org.apache.hadoop.dfs.NameNode.isDir on
namen |
United States |
2007-03-29 13:41:25 |
[ https://issues.apache.org/jira/browse/HADOOP-1178?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1178:
-------------------------------------
Attachment: (was: namenodestart.patch)
> NullPointer Exception in
org.apache.hadoop.dfs.NameNode.isDir on namenode restart
>
------------------------------------------------------------
---------------------
>
> Key: HADOOP-1178
> URL: htt
ps://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: namenodestart2.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(NativeMethodAcce
ssorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
|
|