[HADOOP-1695] Secondary Namenode halt when SocketTimeoutException at startup

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.12.3
• Fix Version/s: 0.15.0
• Assignee: Dhruba Borthakur
• Reporter: Koji Noguchi
• Created: 08/Aug/07 21:28
• Updated: 08/Jul/09 16:42
• Resolved: 04/Oct/07 18:31

Description

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)