[
https://issues.apache.org/jira/browse/HADOOP-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644937#action_12644937
]
Hadoop QA commented on HADOOP-4552:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393108/HADOOP-4552.patch
against trunk revision 709609.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3524/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3524/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3524/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3524/console
This message is automatically generated.
> Deadlock in RPC Server
> ----------------------
>
> Key: HADOOP-4552
> URL: https://issues.apache.org/jira/browse/HADOOP-4552
> Project: Hadoop Core
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.16.3
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.19.1, 0.20.0
>
> Attachments: HADOOP-4552.patch
>
>
> RPC server could get into a deadlock especially when clients or server are
> network starved. This is a deadlock between RPC responder thread trying to
> check if there are any connection to be purged and RPC handler trying to
> queue a response to be written by the responder.
> This was first observed [this
> thread|http://www.nabble.com/TaskTrackers-disengaging-from-JobTracker-to20234317.html].
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
