[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-dev
Subject:    [jira] Updated: (HADOOP-312) Connections should not be cached
From:       "Devaraj Das (JIRA)" <jira () apache ! org>
Date:       2006-06-30 18:56:30
Message-ID: 33055827.1151693790668.JavaMail.jira () brutus
[Download RAW message or body]

     [ http://issues.apache.org/jira/browse/HADOOP-312?page=all ]

Devaraj Das updated HADOOP-312:
-------------------------------

    Attachment: config_connection_cache.patch

Modified the datanode Heartbeat logic to allow the datanodes to choose a random \
heartbeat interval between specified limits (the range, after some calculations on \
the constants defined in FSconstants.java, is between 3 sec and 103 sec).

> Connections should not be cached
> --------------------------------
> 
> Key: HADOOP-312
> URL: http://issues.apache.org/jira/browse/HADOOP-312
> Project: Hadoop
> Type: Improvement

> Components: ipc
> Versions: 0.4.0
> Reporter: Devaraj Das
> Attachments: config_connection_cache.patch
> 
> Servers and clients (client include datanodes, tasktrackers, DFSClients & tasks) \
> should not cache connections or maybe cache them for very short periods of time. \
> Clients should set up & tear down connections to the servers everytime they need to \
> contact the servers (including the heartbeats). If connection is cached, then reuse \
> the existing connection for a few subsequent transactions until the connection \
> expires. The heartbeat interval should be more so that many more clients (order of  \
> tens of thousands) can be accomodated within 1 heartbeat interval.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]