[
https://issues.apache.org/jira/browse/HADOOP-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630244#action_12630244
]
Hadoop QA commented on HADOOP-4062:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389450/closeSync.patch
against trunk revision 693705.
+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 appears to introduce 1 new Findbugs warnings.
+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/3244/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3244/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3244/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3244/console
This message is automatically generated.
> IPC client does not need to be synchronized on the output stream when a
> connection is closed
> --------------------------------------------------------------------------------------------
>
> Key: HADOOP-4062
> URL: https://issues.apache.org/jira/browse/HADOOP-4062
> Project: Hadoop Core
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.18.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.19.0
>
> Attachments: closeSync.patch
>
>
> Currently when a connection on the client side is closed, the close method is
> synchronized on the output stream. The synchronization is not necessary and
> has introduced a side effect that the socket can not be closed immediately
> when meanwhile applications are sending large requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
