You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2013/10/22 03:32:42 UTC

[jira] [Commented] (HDFS-5400) DFS_CLIENT_MMAP_CACHE_THREAD_RUNS_PER_TIMEOUT constant is set to the wrong value

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

Andrew Wang commented on HDFS-5400:
-----------------------------------

+1

> DFS_CLIENT_MMAP_CACHE_THREAD_RUNS_PER_TIMEOUT constant is set to the wrong value
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-5400
>                 URL: https://issues.apache.org/jira/browse/HDFS-5400
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-5400.001.patch
>
>
> {{DFS_CLIENT_MMAP_CACHE_THREAD_RUNS_PER_TIMEOUT}} is set to the wrong value.  It should be set to {{dfs.client.mmap.cache.thread.runs.per.timeout}}, but instead it is set to {{dfs.client.mmap.cache.timeout.ms}}.  The result is that mmap segments cached in the {{ClientMmapManager}} will take much longer to timeout than they should.



--
This message was sent by Atlassian JIRA
(v6.1#6144)