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

Posted to hdfs-dev@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/10/22 02:03:41 UTC

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

Colin Patrick McCabe created HDFS-5400:
------------------------------------------

             Summary: 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)