Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <217678629.26271264464514688.JavaMail.jira@brutus.apache.org>
Date: Tue, 26 Jan 2010 00:08:34 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6459) IPC server should set SO_KEEPALIVE
 to the accepted sockets
In-Reply-To: <1093819616.1261187418255.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804803#action_12804803 ] 

Hudson commented on HADOOP-6459:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #148 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/148/])
    . IPC client bug may cause rpc call hang. Contributed by Hairong Kuang.


> IPC server should set SO_KEEPALIVE to the accepted sockets
> ----------------------------------------------------------
>
>                 Key: HADOOP-6459
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6459
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.1
>            Reporter: Qi Liu
>         Attachments: HADOOP-6459.0.20.patch, HADOOP-6459.patch
>
>
> When there is some unexpected network outage or client-side issue, the network connection could stay alive forever, due to the lack of keep alive. We have observed such dead connection in name node. Though it has no known performance hits, but it is a waste of resource. Adding SO_KEEPALIVE to all accepted sockets should not be heavy, since the keep alive TCP packets will only be sent once every four hours.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.