Re: dfs.datanode.socket.reuse.keepalive

or dropping the client side expiry down to something like 1-2 seconds. >>> I'd rather do that than up the server side, since the server side resource >>> (DN threads) is likely to be more contended. >>> >>> -Todd >>> >>> On Fri, Jun 7, 2013 at 4

Re: dfs.datanode.socket.reuse.keepalive

source >> (DN threads) is likely to be more contended. >> >> -Todd >> >> On Fri, Jun 7, 2013 at 4:29 PM, Colin McCabe wrote: >> >>> Hi all, >>> >>> HDFS-941 added dfs.datanode.socket.reuse.keepalive. This allows >>> DataXcei

[jira] [Created] (HDFS-4911) Reduce PeerCache timeout to be commensurate with dfs.datanode.socket.reuse.keepalive

Colin Patrick McCabe created HDFS-4911: -- Summary: Reduce PeerCache timeout to be commensurate with dfs.datanode.socket.reuse.keepalive Key: HDFS-4911 URL: https://issues.apache.org/jira/browse/HDFS-4911

Re: dfs.datanode.socket.reuse.keepalive

the server side resource > (DN threads) is likely to be more contended. > > -Todd > > On Fri, Jun 7, 2013 at 4:29 PM, Colin McCabe wrote: > >> Hi all, >> >> HDFS-941 added dfs.datanode.socket.reuse.keepalive. This allows >> DataXceiver worker threads i

Re: dfs.datanode.socket.reuse.keepalive

HDFS-941 added dfs.datanode.socket.reuse.keepalive. This allows > DataXceiver worker threads in the DataNode to linger for a second or > two after finishing a request, in case the client wants to send > another request. On the client side, HDFS-941 added a SocketCache, so > that subsequent clien

dfs.datanode.socket.reuse.keepalive

Hi all, HDFS-941 added dfs.datanode.socket.reuse.keepalive. This allows DataXceiver worker threads in the DataNode to linger for a second or two after finishing a request, in case the client wants to send another request. On the client side, HDFS-941 added a SocketCache, so that subsequent