[ 
https://issues.apache.org/jira/browse/HDFS-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893080#comment-13893080
 ] 

Hadoop QA commented on HDFS-4911:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12627288/HDFS-4911.001.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/6047//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6047//console

This message is automatically generated.

> Reduce PeerCache timeout to be commensurate with 
> dfs.datanode.socket.reuse.keepalive
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-4911
>                 URL: https://issues.apache.org/jira/browse/HDFS-4911
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>         Attachments: HDFS-4911.001.patch
>
>
> The default timeout for the client's PeerCache is much longer than the 
> DataNode would possibly keep the socket open.  Specifically, 
> {{dfs.client.socketcache.expiryMsec}} defaults to 2 *
> 60 * 1000 (2 minutes), whereas {{dfs.datanode.socket.reuse.keepalive}}
> defaults to 1000 (1 second).  We should make these more similar to minimize 
> situations where the client tries to use sockets which have gone stale.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to