hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eric baldeschwieler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-312) Connections should not be cached
Date Fri, 30 Jun 2006 19:41:30 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-312?page=comments#action_12418699 ] 

eric baldeschwieler commented on HADOOP-312:
--------------------------------------------

Could we break the datanode heartbeat thing you are doing into another bug?  It seems unrelated
to a redesign of our general IPC and this bug is not complete enough on the motivation of
your work for me to understand why randomizing heartbeat intervals is a good idea.

> 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


Mime
View raw message