[
https://issues.apache.org/jira/browse/HADOOP-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728851#action_12728851
]
Hadoop QA commented on HADOOP-6099:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12412894/ipcPing2.txt
against trunk revision 791937.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
-1 release audit. The applied patch generated 260 release audit warnings
(more than the trunk's current 258 warnings).
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/558/testReport/
Release audit warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/558/artifact/trunk/current/releaseAuditDiffWarnings.txt
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/558/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/558/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/558/console
This message is automatically generated.
> Allow configuring the IPC module to send pings
> ----------------------------------------------
>
> Key: HADOOP-6099
> URL: https://issues.apache.org/jira/browse/HADOOP-6099
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.21.0
>
> Attachments: ipcPing.txt, ipcPing2.txt
>
>
> The IPC Client sets a socketTimeout for the time period specified by the
> pingInterval and then sends a ping every pingInterval. This means that if a
> RPC server does not respond to a RPC client, then the RPC client blocks
> forever. This is a problem for applications that wants to switch quickly from
> one un-responsive HDFS cluster to a good one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
