hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5400) DFS_CLIENT_MMAP_CACHE_THREAD_RUNS_PER_TIMEOUT constant is set to the wrong value
Date Tue, 22 Oct 2013 15:15:44 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Patrick McCabe updated HDFS-5400:
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 2.3.0
>
>         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)

Mime
View raw message