[
https://issues.apache.org/jira/browse/HADOOP-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532499
]
Hadoop QA commented on HADOOP-1695:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12367046/socketTimeout2.patch
against trunk revision r581745.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/885/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/885/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/885/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/885/console
This message is automatically generated.
> 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
> Assignee: dhruba borthakur
> Priority: Blocker
> Fix For: 0.15.0
>
> Attachments: socketTimeout2.patch
>
>
> 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.
