[
https://issues.apache.org/jira/browse/HDFS-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801417#comment-13801417
]
Hadoop QA commented on HDFS-5400:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12609559/HDFS-5400.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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/5252//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5252//console
This message is automatically generated.
> 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)
