[
https://issues.apache.org/jira/browse/HDFS-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802782#comment-13802782
]
Hudson commented on HDFS-5400:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #371 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/371/])
HDFS-5400. DFS_CLIENT_MMAP_CACHE_THREAD_RUNS_PER_TIMEOUT constant is set to the
wrong value (Colin Patrick McCabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1534655)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
> 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)
