Secondary Namenode halt when SocketTimeoutException at startup
--------------------------------------------------------------
Key: HADOOP-1695
URL: https://issues.apache.org/jira/browse/HADOOP-1695
Project: Hadoop
Issue Type: Bug
Components: dfs
Affects Versions: 0.12.3
Reporter: Koji Noguchi
When we start the namenode and secondary-namenode at the same time, usually
primary namenode is busy handling the blockreports.
If secondary namenode fail to connect at startup, it crashes leaving the
following exception in the .out file.
I hope it will catch the exception and retry later.
Exception in thread "main" java.net.SocketTimeoutException: timed out waiting
for rpc response
at org.apache.hadoop.ipc.Client.call(Client.java:471)
at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:163)
at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:247)
at org.apache.hadoop.dfs.SecondaryNameNode.<init>(SecondaryNameNode.java:96)
at org.apache.hadoop.dfs.SecondaryNameNode.main(SecondaryNameNode.java:474)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
