You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2008/09/03 21:05:44 UTC

[jira] Updated: (HADOOP-4062) IPC client does not need to be synchronized on the output stream when a connection is closed

     [ https://issues.apache.org/jira/browse/HADOOP-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HADOOP-4062:
----------------------------------

    Attachment: closeSync.patch

This patch removes the synchronization on "out" in Client.Connection.close(). Additionally it does the following:
1. Does not set in and out to be null after they are closed;
2. As a result of 1, no need to set "out" to be an atomic reference;
3. Removes a confusing exception when a client is stopped but there is no pending RPC.

> 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.